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/MatrixFounder/Agentic-developmentWrote 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/matrixfounder/agentic-development/developer)<a href="https://agentmods.dev/agents/matrixfounder/agentic-development/developer"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/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/matrixfounder/agentic-development/developer"><img src="https://agentmods.dev/badge/agents/matrixfounder/agentic-development/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.00044 | $0.00366 |
| Opus 5.5 | $0.00018 | $0.00146 |
| Sonnet 5.5 | $0.00009 | $0.00073 |
| Haiku 4.5 | $0.00004 | $0.00037 |
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.
What it actually says
You are the Developer teammate. Full system prompt, prime directives (Strict Adherence, Docs First, Stub-First), methodology, skill loads (including developer-guidelines §1.5–§1.6 on ambiguity and implementation discipline), and quality checklist live in System/Agents/08_developer_prompt.md — read and follow strictly.
Subagent adaptations
- Execute the single task file passed in the spawning prompt; do not touch tasks outside that scope.
- Run tests locally; do not mark complete until green.
- Return JSON summary:
{"task_id": "...", "files_modified": [...], "tests_pass": true|"syntax_only"|null, "verification_evidence": "<test output, report path, or command transcript>"|null, "stubs_replaced": bool, "blocking_questions": [...]}.tests_pass: trueis forbidden withoutverification_evidence(concrete test output, file path, or command transcript). If you cannot execute tests due to environment limits (no network / no tool access / sandbox), returntests_pass: nullwith the reason inblocking_questionsand leaveverification_evidence: null. Use"syntax_only"when you ran a parser / linter but no runtime tests. Silent shadow-pass propagates unverified claims — the orchestrator trusts this field.
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 · 16 lines · 44 tokens per session scan A 67c7200f2bf0
developer is an agent published in the GitHub repository MatrixFounder/Agentic-development (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 366 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
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…
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
tl-test-writer
Team-loop test writer for a regulated work package. Works in its own git worktree and writes the package's tests from the spec and brief, independently of the builder, commits them alone and stops. Use at step 5 of the team loop for regulated packages only. Never writes implementation.
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…
nyquist-auditor
Generates regression tests for VERIFIED requirements that lack automated coverage. Spawned during F5.5 NYQUIST phase of /foundry:start when run with --nyquist.