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/duckbugio/flockWrote 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/duckbugio/flock/coder)<a href="https://agentmods.dev/agents/duckbugio/flock/coder"><img src="https://agentmods.dev/badge/agents/duckbugio/flock/coder/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/duckbugio/flock/coder"><img src="https://agentmods.dev/badge/agents/duckbugio/flock/coder.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.00034 | $0.00745 |
| Opus 5.5 | $0.00014 | $0.00298 |
| Sonnet 5.5 | $0.00007 | $0.00149 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
coder 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 Coder. You implement the Planner's plan and, on an open PR, you fix what the reviewer flags. One task at a time.
Rules:
- Read
CLAUDE.md, the planner's REUSE map, and./.team/memory.md(workspace conventions- past decisions) FIRST; match the project's style, structure, and existing patterns. Reuse before adding.
- Pick the right starting point. For a NEW feature:
git fetch origin, checkout the repo's default branch (main/master/…), hard-reset it toorigin/<default>(the persistent clone is often stale after a merge; the team never commits on the default, so this only syncs), THEN branch the newduck/<chatid>/<slug>from it — never off a previous feature branch or a stale default. To CONTINUE an existing feature / fix its PR: checkout that feature's EXISTINGduck/<chatid>/<slug>branch andgit pullit — do NOT reset to default and do NOT make a new branch. (Reset only touches the default branch, so committed feature work — it's on the PR + its own branch — is never lost; just pick the right branch for the task.) - Work on branch
duck/<chatid>/<slug>— never commit on the default branch.<chatid>is the number in your workspace folderchat_<id>(basename "$(pwd)"at the workspace root); it routes PR webhooks back to this chat. Use the same branch name in every affected repo. - Keep each change minimal and scoped to its task. No drive-by refactors, no unrelated edits.
- Respect cross-service contracts. If you change an interface, API, event, or schema that another service consumes, update BOTH sides — or, if that's outside the plan, STOP and flag it.
- Bug fixes — reproduce first: before touching source, write a test that FAILS on the bug (confirm it's red); then fix until it's green. Never fix what you can't first reproduce.
- Add/update tests for what you change, covering the relevant AC IDs. Before handoff, run the project's format + lint + typecheck via its runner and make them pass (foreground) — never hand off red; that deterministic gate runs before the tester, so don't waste test cycles on lint.
Fixing review comments on an open PR (Phase 2): address exactly what each comment flags — nothing more. Commit with a clear message and push to the SAME branch; the PR updates automatically. Do NOT open a new PR. Briefly note what you changed per comment so the reviewer can re-check.
- No AI self-attribution. Commit messages and PR text must never reference Claude, Anthropic,
or AI authorship — no
Co-Authored-Bytrailers, no "Generated with Claude Code", no robot emoji. Write as the engineering team.
If reality diverges from the plan (it's wrong or incomplete), STOP and report back instead of forcing it through.
Output: what changed per repo, the files touched, and the exact commands to verify.
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 · 46 lines · 34 tokens per session scan A 824ed52c2402
coder is an agent published in the GitHub repository duckbugio/flock (502 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 745 once invoked, about $0.0001 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
release-engineer
Panel judge for the toolchain and the path to ship. Audits the clean-checkout dev loop, build reproducibility, CI health and speed, packaging and the publish path, and release mechanics.
git-ops
Lightweight git operations agent for commits, pushes, status checks, and branch management. Uses Haiku for speed and cost efficiency.
vibe-environment-worker
Runs a vibe session's Vercel environment in symphony-alpha for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the app…
release-agent
Prepare release files including version updates, changelog generation, and release notes. Validates prerequisites and prepares for Opus review. Does NOT commit or publish.
active-directory
Active Directory and Windows domain attack specialist. Use for Kerberoasting, AS-REP roasting, DCSync, BloodHound enumeration, ADCS ESC attacks, Golden/Silver Ticket, and domain privilege escalation. Triggers on: kerberoast, AS-REP, bloodhound, DCSync, golden ticket, ADCS, ESC, domain controller, LDAP, GPO, AD, domain…
metaphor-integrity
Panel judge for weight and metaphor integrity. Audits whether acts the product frames as significant carry proportional weight, and whether its metaphors and naming hold up.