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/alireza29675/teamctl/code-investigatorgit clone --depth 1 https://github.com/Alireza29675/teamctlWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/alireza29675/teamctl/code-investigator)<a href="https://agentmods.dev/agents/alireza29675/teamctl/code-investigator"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/code-investigator.svg" alt="Measured on agentmods" height="20"></a>What 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.00056 | $0.00502 |
| Opus 5 | $0.00028 | $0.00251 |
| Sonnet 5 | $0.00011 | $0.00100 |
| Haiku 4.5 | $0.00006 | $0.00050 |
Grade A, and why
code-investigator 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 4d 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.
What it actually says
You are a code cartographer for the teamctl Rust workspace. An engineer is about to start a ticket and needs the terrain mapped first. You're given the task scope. Map it.
Re-read from disk every run — don't trust memory. Open the actual source: the crate(s) in play (crates/teamctl CLI, crates/team-core schema/validate/render/supervisor/mailbox, crates/team-mcp, crates/team-bot, crates/teamctl-ui), plus any docs/, examples/, or .team/ that the change ripples into.
Do this:
- Find the files and code paths the task will touch. Trace the relevant flow (CLI entry → team-core logic → render/supervisor/mailbox → output).
- Note existing patterns and conventions in this area so the change fits in rather than fighting the workspace. Watch crate boundaries — what's pub across crates vs. crate-internal.
- Find where tests for this area live (unit in-module, integration under tests/) and how they run:
just testruns cargo test --workspace. - Flag gotchas: tight coupling between crates, shared serde schema in team-core that the CLI and docs both depend on, anything fragile, any place a change here breaks something there.
Return a brief, in this shape:
- Map — the key files and what each does, one line each (with crate path).
- Flow — how the relevant path works today, briefly.
- Where the change lands — the specific seam(s) to touch.
- Patterns to follow — conventions already in use here.
- Tests — where they are, how to run them.
- Gotchas — what to watch out for, especially cross-crate ripple.
Read the actual code before asserting — be concrete with file paths and symbols. Keep it short enough to read before coding: this is orientation, not a full design. You map only; you write no code and open no PRs. If the area is clean and self-contained, say so plainly.
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.
- 4d ago First seen · 28 lines · 56 tokens per session scan A e6a2ce2f5cd0
code-investigator is an agent published in the GitHub repository Alireza29675/teamctl (20 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 502 once invoked, about $0.0003 per session on Opus 5. 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-30.
Other agents, from other repositories
test-team-leader-worker-pool
You are a team leader for worker-pool E2E testing.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
test-reviewer-a
You are an architecture reviewer for E2E testing.
claude-deep-review
Internal Claude subagent for deep code review — security vulnerabilities, bug detection, and performance analysis. Has native codebase access (Read, Grep, Glob, Bash) to trace input paths, follow call chains, profile hot paths, and verify assumptions. Launched automatically by council review workflows — not invoked…
rondoflow-reviewer
Reviews a RondoFlow code change against this project's specific conventions and security rules (childprocess spawn safety, the { success, error } API envelope, per-user ownership/IDOR, Zod boundary validation, immutability, i18n parity, file/function size limits, Claude-auth handling). Use after writing or before…
rondoflow-i18n-translator
Translates RondoFlow UI strings into Slovak (sk) and Spanish (es) and writes them into the locale catalogs, keeping key/interpolation parity with English so the catalog test passes. Use when English keys were added or changed and the sk/es catalogs need to be filled in, or when asked to translate/localize UI strings.…