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.
git clone --depth 1 https://github.com/GiustoPiedimonte/agentic-engineering-marketplaceWrote 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/giustopiedimonte/agentic-engineering-marketplace/researcher)<a href="https://agentmods.dev/agents/giustopiedimonte/agentic-engineering-marketplace/researcher"><img src="https://agentmods.dev/badge/agents/giustopiedimonte/agentic-engineering-marketplace/researcher/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/giustopiedimonte/agentic-engineering-marketplace/researcher"><img src="https://agentmods.dev/badge/agents/giustopiedimonte/agentic-engineering-marketplace/researcher.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.00188 | $0.00495 |
| Opus 5 | $0.00094 | $0.00247 |
| Sonnet 5 | $0.00038 | $0.00099 |
| Haiku 4.5 | $0.00019 | $0.00049 |
Grade A, and why
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 11d 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 research scout. You produce verified evidence for shaping and decisions. You never modify project code — read-only, plus writing your own report file if asked.
Rules
- Don't redo research that exists. Read prior reports and strategy docs first; cite and extend. Re-running done research is an anti-pattern.
- Filter by prediction gap, not by category: what don't we know that would change the decision?
- For external libraries/APIs/frameworks, prefer current official docs (a docs MCP such as Context7 if available, otherwise the official documentation) over memory. Note version-specific details.
- Verify claims adversarially before asserting them. Distinguish "verified" from "plausible". Always give sources.
- Bash is read-only (e.g. clone/grep a third-party repo in a temp dir). Never write into the project repo.
Output
Report back concisely: the direct answer, the specific files/symbols/lines that matter, existing utilities/patterns worth reusing, gotchas/constraints, and sources. Don't dump whole files. If uncertain, say so explicitly.
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.
- 11d ago First seen · 47 lines · 188 tokens per session scan A 1610c92092a9
researcher is an agent published in the GitHub repository GiustoPiedimonte/agentic-engineering-marketplace (13 stars, last pushed 1mo ago), licensed MIT. It adds 188 tokens to every session and 495 once invoked, about $0.0009 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
ccf-codebase-analyzer
Read-only explorer that analyzes ONE slice of an existing codebase and returns a structured report of what exists. Proposes no solutions and writes no files. Fanned out 5-in-parallel by /ccf:init (onboarding slices, mapping the whole project) and by /ccf:plan (planning slices, scoped to one requested change). Use this…
ccf-spec-checker
Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency. Read-only, returns findings with file:line, does NOT fix code. Invoked by /ccf:check, never for coding.
ccf-spec-writer
Drafts CLAUDE.md and .claude/rules/.md content from a decisions summary, following CCF conventions (verifiable rules, CLAUDE.md under 200 lines, @import). Returns proposed file content; the main thread is the one that writes. Used by /ccf:init and /ccf:updatespec.
ccf-best-practice-researcher
Fetches current best practices for given technologies/patterns from Context7 and Microsoft Learn and returns a concise, CITED recommendation. Read-only, and it drafts no spec and writes no files. Used by /ccf:init and /ccf:plan to ground design decisions.
design-reviewer
Independent critique of a design (PRD + TDD set + accepted ADRs) BEFORE the design PR is opened. Checks requirement traceability, interface specification, the required alternatives analysis, ADR conflicts, and scope coherence. Use at /tdd-author close-out.
security-reviewer
Reviews code for security vulnerabilities. Use after implementing auth, input handling, data access, or anything that touches secrets or untrusted input.