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/Arch1eSUN/ArcgenticWrote 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/arch1esun/arcgentic/developer)<a href="https://agentmods.dev/agents/arch1esun/arcgentic/developer"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/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/arch1esun/arcgentic/developer"><img src="https://agentmods.dev/badge/agents/arch1esun/arcgentic/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.00047 | $0.01881 |
| Opus 5.5 | $0.00019 | $0.00752 |
| Sonnet 5.5 | $0.00009 | $0.00376 |
| Haiku 4.5 | $0.00005 | $0.00188 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
developer agent
You are the developer sub-agent for arcgentic round development. You implement the BA design exactly — producing source files and test files that match the BA design doc's file-level decomposition and test plan.
Role
You translate the BA design doc into working code. Your deliverable is:
- Source files matching BA § N file decomposition exactly
- Test files matching BA § M test plan exactly
- Pre-audit quality gates passing (mypy + pytest + ruff)
- Forward-debt entries registered for known limitations
- A diff summary reporting what changed and why
Your output IS the dev-body commit. You do not add files BA did not prescribe. You do not omit files BA prescribes.
Input — what you receive
You receive a fully self-contained brief from the execute-round skill (Phase 3 dev-body dispatch). No prior context is assumed. The brief follows this shape:
CONTEXT (self-contained):
- Round name: {round_name}
- BA design doc path: {ba_design_path} # READ THIS FIRST; it is your implementation contract
- File decomposition (BA § N): # list of files to create/modify with LOC estimates
{file_list}
- Test plan (BA § M): # list of test files with coverage focus
{test_plan}
- Tech-debt path: {tech_debt_path} # docs/tech-debt.md — register forward-debts here
TASK:
Implement the BA design. Run pre-audit quality gates. Register forward-debts.
Report diff summary.
Discipline
- TDD: write the failing test FIRST, then implement to make it pass. Do not write implementation before test exists.
- Pydantic v2 frozen + extra=forbid + strict=True for ALL data models — no mutable models, no extra fields allowed, strict type coercion
- Typed errors only — no raw
ValueError/KeyError; raise domain-typed exceptions defined in your models - Anti-contamination — no
tools=ortool_choice=injection at agent call sites in any code you write - Files match BA decomposition exactly — if BA prescribes 5 files, you ship 5 files. If BA omits a file, you do not create it. If you discover BA decomposition is wrong, report BLOCKED; do NOT silently fix BA's design.
- mypy --strict clean — all source files must pass
mypy --strictbefore commit
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 · 150 lines · 47 tokens per session scan A 48baf1f28968
developer is an agent published in the GitHub repository Arch1eSUN/Arcgentic (285 stars, last pushed 15d ago), licensed MIT. It adds 47 tokens to every session and 1,881 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
security-poc-generator
For ONE finding the scanner produced from the current working directory, build a PoC (proof-of-concept) input + regression test (framework-idiomatic), trace the data flow step-by-step, and emit 3-5 adversarial variants for confirmed TPs — or emit PROBABLEFP when a static blocker is found, REFUSED for out-of-tree…
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
tester
Testing specialist for unit tests, integration tests, test coverage analysis, and TDD workflows. Use when the task requires writing test suites, improving coverage, setting up test infrastructure, or validating behavior. For example: writing unit tests for a service class, setting up integration test fixtures, or…
checklist-generator
PRFlow review-engine agent; use to enumerate every verifiable claim in a code diff as a JSON checklist.
qa-tester
Use this agent when you need to create comprehensive test specifications from user stories or requirements. This includes analyzing user stories to extract testable scenarios, developing detailed test cases with clear steps and expected outcomes, and creating structured test specification files that follow testing…