Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add agents/nxtg-ai/forge-plugin/detectivegit clone --depth 1 https://github.com/nxtg-ai/forge-pluginWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00000 | $0.01969 |
| Opus 5 | $0.00000 | $0.00984 |
| Sonnet 5 | $0.00000 | $0.00394 |
| Haiku 4.5 | $0.00000 | $0.00197 |
Grade A, and why
detective scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Detective
Sherlock Holmes for codebases -- performs deep project analysis, technology detection, gap analysis, and health scoring across five quality dimensions.
| Level | L1 Vibe Coder |
| Category | Governance & Analysis |
| Model | Sonnet |
What It Does
The Detective is a forensic analyst for your codebase. It does not fix things -- it finds things. When invoked, it performs a structured investigation across five dimensions (testing, security, documentation, architecture, git practices) and produces a scored health report with prioritized recommendations. Every finding is backed by evidence: file paths, line numbers, specific metrics.
What separates the Detective from running npm audit and eslint yourself is synthesis. It does not just list problems -- it weighs them. A codebase with 95% test coverage but three hardcoded API keys gets a different priority ranking than one with zero vulnerabilities but 40% coverage. The Detective calculates a weighted health score (Testing 30%, Security 25%, Architecture 20%, Documentation 15%, Git Practices 10%) and presents a single number (0-100) that captures your project's overall health. More importantly, it ranks the recommended actions by impact, so you know what to fix first.
The Detective also handles technology stack detection. Hand it an unfamiliar codebase and it identifies languages, frameworks, databases, external services, build tools, and development patterns. It checks against best-practice checklists for each detected stack (Python projects should have type hints and pytest; TypeScript projects should have strict mode and ESLint) and reports gaps. This makes it the ideal first agent to run on a new project or when onboarding.
When to Use It
- Evaluating a new codebase: When you inherit a project or join a team and need to understand what you are working with -- tech stack, quality level, architectural patterns, and where the skeletons are buried.
- Running a health check: When the Orchestrator delegates Option 4 (Health Check) and you need a comprehensive quality assessment across all dimensions.
- Before a major refactoring: When you need hard data about current code quality, complexity hotspots, and test coverage gaps to justify and scope a refactoring effort.
- Investigating a vague problem: When something feels wrong -- "the code is slow" or "things keep breaking" -- but you cannot pinpoint why. The Detective's structured analysis finds the patterns.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 132 lines · 0 tokens per session scan A 1d3343ad405d
detective is an agent published in the GitHub repository nxtg-ai/forge-plugin (5 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,969 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
code-reviewer
Reviews code for project guideline compliance, bugs, and quality issues. Use after writing code, before commits, or before PRs. Specify files to review or defaults to unstaged git changes. High-confidence issues only (80+) to minimize noise.
docs-impact
Reviews documentation affected by code changes. Identifies stale docs, removed feature references, and missing entries for new user-facing features. Reports findings with specific fixes. Advisory only - does not modify files.
scout
MUST be used for exploratory codebase research, rapid code analysis, and broad pattern searches. Fast read-only scout returning compressed context for handoff.
claude-design-orchestrator
Parses claude.ai/design handoff bundles: validates schema, dedups proposed components against the codebase via component-search, reconciles tokens, and tracks bundle→PR provenance so design intent stays linked to shipped code.
database-engineer
PostgreSQL specialist: schema design, migrations, query optimization, pgvector/full-text search, Alembic migrations.
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.