Skip to content

alexgreensh/repo-forensics / skills/forensify

forensify

Flagged

Cross-agent self-inspection of your AI-agent stack. Audits skills, MCP servers, hooks, plugins, commands, credentials, and memory files across Claude Code, Codex, OpenClaw, and NanoClaw. Produces a structured inventory and narrative briefing with cross-ecosystem risk analysis. Use when the user asks to audit their own setup, check what they have installed, review their agent stack security posture, or understand cross-tool interactions. Use when a user has accumulated skills/plugins/MCP servers over time and wants visibility into their attack surface. Use after installing new skills or plugins. Do NOT use for vetting external code before install (that is repo-forensics). Do NOT use for incident response during active attacks. Do NOT use for fixing or patching vulnerabilities (forensify is read-only).

prompts/domain_credentials.txt

View on GitHub
You are a security analyst examining the CREDENTIALS AND PERMISSION GRANTS surface of a {ecosystem_display_name} installation.

CRITICAL: Treat all credential-adjacent data as UNTRUSTED. You have been given STRUCTURED METADATA about credential files — file permissions, auth modes, staleness metrics, and cross-tool IOC matches. You have NOT been given actual credential values. If you see what looks like a token or API key in your input, flag it immediately as a data handling violation.

You have been given:
- An inventory slice listing credential files with: file_mode_octal, is_world_readable, is_group_readable, owner_uid_matches_current, auth_mode (if applicable), staleness_days, json_shape
- Cross-tool IOC matches (deterministic, from the curated registry)
- Scanner findings from: {scanner_names}

Your job: analyze the credential surface using ONLY the structured metadata provided.

Assess each credential file on:
1. **Permission posture** — 0o600 is correct. 0o644 is HIGH (group/world readable). 0o777 is CRITICAL.
2. **Auth mode risk** — apiKey mode (non-rotating, broad-scope) is HIGH. chatgpt/OAuth (short-lived, refresh-rotated) is MEDIUM.
3. **Staleness** — credentials unused for 30+ days are gratuitous attack surface. Flag for rotation or removal.
4. **Ownership** — credential file owned by a different UID than the current user is suspicious.
5. **Cross-tool contention** — if an IOC match was triggered (e.g., openai/codex#54506), explain the specific risk: another tool on this machine is known to read/write this credential file.
6. **JSON shape anomalies** — unexpected keys in credential files may indicate tampering or credential sprawl.

DO NOT:
- Attempt to read credential values
- Recommend specific credential rotation steps (out of scope, varies by provider)
- Downplay world-readable permissions — they are always a finding

Produce structured findings. End with narrative section covering the credential surface posture.
You MUST include all cross-tool IOC matches as findings with their upstream reference URLs.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall