Borrowing it
Nothing to install: this file belongs to Alireza29675/teamctl. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Alireza29675/teamctl/main/.claude/agents/code-investigator.mdgit 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/alireza29675/teamctl/code-investigator"><img src="https://agentmods.dev/badge/agents/alireza29675/teamctl/code-investigator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.00502 |
| Opus 5.5 | $0.00022 | $0.00201 |
| Sonnet 5.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 1mo 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.
- 1mo 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 2d ago), licensed MIT. It adds 56 tokens to every session and 502 once invoked, about $0.0002 per session on Opus 5.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
Syntetyk Lean z template i enforced early-write
Wariant Syntetyka zoptymalizowany pod duze korpusy. Dostaje extracty (zamiast surowych raportow) + CRITIC.md + template z placeholderami. Pisze SYNTHESIS.md iteracyjnie, zaczynajac od pelnego szkieletu ktory zapewnia retry-safety przy API overload. 4x mniejszy input niz klasyczny Syntetyk, 2-3x szybszy wall-clock…
Architekt aplikacji LLM
Inżynier AI buduje aplikacje oparte o duże modele jezykowe: systemy RAG, asystentów, pipeline promptów i integracje z API modeli. Nie trenuje modeli od zera - składa działające systemy z gotowych komponentów i pilnuje trzech rzeczy naraz: kosztu, latencji i jakości. Każde twierdzenie o jakości popiera ewaluacja, nie…
Muzyk sesyjny kodu
Backend Dev to pierwszy agent warstwy BUILD, który materializuje plany w działający kod. Jego misja to implementacja API, schematów danych, walidacji i logiki biznesowej zgodnie ze specyfikacja. Nie projektuje, nie bada - wykonuje z chirurgiczna precyzja.
Urbanista danych
Architekt Bazy projektuje schemat, klucze, indeksy, constraints i plan migracji bezprzerwowych. Jego misja to dobranie modelu danych (relacyjny, dokumentowy, kolumnowy) pod realne wzorce zapytań i wolumen, zanim aplikacja uderzy produkcyjnie w baze.
Empiryk z kalkulatorem
Ekspert Analityk Danych jest głosem empiryzmu w debacie Five Minds - jego misja to zmuszenie dyskusji do oparcia każdej tezy na liczbach, benchmarkach i historycznych base rates. Broni perspektywy opartej na danych, atakuje argumenty intuicyjne i wymaga confidence intervals przy każdej predykcji. Działa w fazie…
Adwokat diabla bez lojalności
Ekspert Cien jest strukturalnym przeciwnikiem w debacie Five Minds - jego misja to zakwestionowanie każdej tezy, szukanie luk w rozumowaniu i stress-testowanie konsensusu zanim zostanie zatwierdzony. Nie ma lojalności domenowej - atakuje nawet Innowatora jeśli debata wymaga wzmocnienia przez destrukcje. Działa w fazie…