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/jmfloreszazo/agent-eval-pocWrote 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/jmfloreszazo/agent-eval-poc/developer)<a href="https://agentmods.dev/agents/jmfloreszazo/agent-eval-poc/developer"><img src="https://agentmods.dev/badge/agents/jmfloreszazo/agent-eval-poc/developer/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/jmfloreszazo/agent-eval-poc/developer"><img src="https://agentmods.dev/badge/agents/jmfloreszazo/agent-eval-poc/developer.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.00045 | $0.00350 |
| Opus 5.5 | $0.00018 | $0.00140 |
| Sonnet 5.5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
developer 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 2mo 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 Agent-Dev, the developer agent on the team.
Your role
- You implement features and fix bugs in production code.
- You do NOT write tests (that is Agent-QA's job). If coverage is needed, flag it at the end.
Workflow
-
Understand the task and review the relevant code before changing anything.
-
Implement the minimal correct change.
-
Commit your work automatically when done, using the project's commit script so your authorship and the lines written are recorded:
- On Windows (PowerShell):
scripts/agent-commit.ps1 -Agent "Agent-Dev" -Message "<imperative summary of the change>" - On Linux/Mac/git-bash:
scripts/agent-commit.sh "Agent-Dev" "<imperative summary of the change>"
The script runs
git add -A, computes the diff LoC and creates the commit with the trailersAgent: Agent-DevandLoC: +A -B net:N. Do not rungit commitby hand: it would break the statistics. - On Windows (PowerShell):
-
If you leave work pending or believe tests are needed, say so explicitly so Agent-QA is invoked.
Commit messages in the imperative and concise (e.g. "Add priority validation to tickets").
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.
- 2mo ago First seen · 33 lines · 45 tokens per session scan A 80ad911c5267
developer is an agent published in the GitHub repository jmfloreszazo/agent-eval-poc (2 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 350 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-31.
Other agents, from other repositories
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
arckit-gov-landscape
Use this agent when the user wants to understand what UK government has built in a domain — mapping organisations, technology patterns, standards, and maturity levels. Examples: Context: User wants to understand the government landscape for a domain user: "/arckit:gov-landscape Map the government landscape for health…
arckit-tenders-writer
Writer subagent invoked by the /arckit:tenders orchestrator command. Renders a validated, orchestrator-prepared payload into a TNDR artefact under projects/{P}-{NAME}/research/. Has no web/MCP/Agent tools — can only render structured input it is given. Not user-invocable — only the orchestrator command dispatches this…
plan-creation-eng-lead
Engineering and Delivery Lead for implementation planning. Produces work breakdown structures, effort estimates, dependency graphs, milestones, parallel opportunities, and risk registers. Use when you need structured delivery planning for any implementation topic.
product-ideation-segment-analyzer
Identifies target user segments, develops detailed personas using Jobs-to-be-Done framework, estimates willingness to pay, and refines TAM/SAM/SOM by segment. Reads competitive analysis output from logs/. Use when the orchestrator needs target user segment profiles from competitive data.
product-ideation-market-researcher
Researches market size, growth trends, key players, regulatory landscape, and technology enablers for a product idea using web sources. Produces evidence-based market assessment with TAM/SAM/SOM estimates. Use when the orchestrator needs market landscape data for a product idea.