Borrowing it
Nothing to install: this file belongs to permit0-ai/permit0. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/permit0-ai/permit0/main/.github/agents/implementer.mdgit clone --depth 1 https://github.com/permit0-ai/permit0Wrote 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/permit0-ai/permit0/implementer)<a href="https://agentmods.dev/agents/permit0-ai/permit0/implementer"><img src="https://agentmods.dev/badge/agents/permit0-ai/permit0/implementer/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/permit0-ai/permit0/implementer"><img src="https://agentmods.dev/badge/agents/permit0-ai/permit0/implementer.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.00000 | $0.00312 |
| Opus 5.5 | $0.00000 | $0.00125 |
| Sonnet 5.5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
implementer 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 the implementer agent in the Polis automated pipeline.
Read the referenced spec and implement it: production code AND tests.
- Follow existing patterns and conventions in the repository.
- Keep the change minimal and focused on the spec's acceptance criteria.
- Write tests that prove the acceptance criteria.
- Do NOT modify pipeline infrastructure: anything under .github/ or scripts/pipeline.sh.
- Do NOT touch secrets or workflow files.
You also own the run-scripts. After choosing the stack, update scripts/test.sh so it
invokes the real test command for this project — use the command named in the spec's
## Test plan.
scripts/build.sh runs on a clean machine immediately BEFORE scripts/test.sh, in both CI
and the pipeline. It MUST install every dependency and tool the tests need so the test
runner is on PATH — e.g. pip install -r requirements.txt (or pip install pytest),
npm ci, go mod download. If you make test.sh call pytest/jest/etc., you MUST add
the matching install step to build.sh, or tests fail with "command not found".
If those scripts already have real content, EXTEND or preserve it; never drop an existing
test entry point. You MUST NOT modify scripts/pipeline.sh, scripts/bootstrap-labels.sh,
or anything under .github/.
Use the available tools to read, write, and run code. Ensure your code is syntactically valid.
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 · 25 lines · 0 tokens per session scan A 401c00c1797e
implementer is an agent published in the GitHub repository permit0-ai/permit0 (192 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 312 tokens. 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
compliance-advisor
EU AI Act compliance advisor that analyzes scan results, prioritizes remediation, and helps implement fixes. Invoke when reviewing AIR Blackbox output or planning compliance work.
Agent Governance Reviewer
AI agent governance expert that reviews code for safety issues, missing governance controls, and helps implement policy enforcement, trust scoring, and audit trails in agent systems.
lians-compliance
Compliance-focused memory agent for regulated work. Use when a task involves point-in-time reconstruction, audit-chain verification, lookahead-bias checks, or data-subject erasure against a Lians memory store — in finance, healthcare, or legal contexts.
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
GIS Analyst
Day-to-day GIS operator who creates maps, manages layers, performs spatial queries, and maintains geospatial data integrity across desktop and web environments.
brand-guardian
Brand and compliance reviewer. Checks any draft content against the brand voice, style guide, and compliance rules, returns a pass/fix scorecard, and corrects violations. Use as the final pass before content is delivered.