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/shopwarelabs/ai-coding-tools/code-researchergit clone --depth 1 https://github.com/shopwareLabs/ai-coding-toolsWhat 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.00086 | $0.00139 |
| Opus 5 | $0.00043 | $0.00069 |
| Sonnet 5 | $0.00017 | $0.00028 |
| Haiku 4.5 | $0.00009 | $0.00014 |
Grade A, and why
code-researcher 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 3d 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
Invoke the researching-code skill with the user's question and return the synthesized findings. Do not enter into user dialogue.
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.
- 3d ago First seen · 11 lines · 86 tokens per session scan A f2b7c2f7a9a9
code-researcher is an agent published in the GitHub repository shopwareLabs/ai-coding-tools (42 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 139 once invoked, about $0.0004 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
skript-agent
Short-Form-Content-Experte für Reels, TikToks, Shorts und Social-Posts. Kein Skript-Bot, sondern strategischer Sparringspartner. Arbeitet auf den echten Daten deiner Nische (5 analysierte Creator) und deinem Voice-Profil, sucht sich auf Wunsch selbst Themen. Triggert auf "schreib mir ein Skript", "Skript zu X", "Reel…
new-hire
Validates documentation by simulating a developer with zero project knowledge. Use when testing README setup instructions, onboarding flows, or auditing documentation quality. PROACTIVELY USE this agent when docs may be outdated.
adversarial-validator
Validates adversarial tests using a 4-phase pipeline (Static Analysis, Dynamic Execution, Oracle Verification, Mutation Testing). Returns structured JSON verdict.
adversarial-generator
Generates adversarial tests that expose real bugs through realistic but challenging inputs. Use when creating tests designed to find logic errors.
adversarial-orchestrator
PROACTIVELY USE this agent to manage adversarial test generation. Coordinates the Generator and Validator in a feedback loop. Use when asked to generate adversarial tests or find bugs.
code-reviewer
Use this agent to review changed files for bugs, security issues, performance problems, and code quality. Use when reviewing PRs, checking code before committing, or auditing code quality. Examples: User: "Review the changes I made" Assistant: "I'll launch the code-reviewer agent to analyze your changes." User: "Is…