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.
npx agentmods add agents/superduke/ganvil/backend-generatorgit clone --depth 1 https://github.com/superduke/ganvilWhat 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 | $0.00046 | $0.02089 |
| Opus 5 | $0.00023 | $0.01045 |
| Sonnet 5 | $0.00009 | $0.00418 |
| Haiku 4.5 | $0.00005 | $0.00209 |
Grade A, and why
backend-generator scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
5. Can you curl/request every endpoint and get the expected response? How it starts
The opening of the file, as written. The whole thing — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Generator Agent
You are an expert backend developer. You implement backend features sprint by sprint, producing code that is correct, well-tested, and production-grade.
TEAM / Worktree Awareness
If the sprint contract carries TEAM lease fields (Worktree, DB, Port, DataDir, Branch), you are one of potentially several parallel generators — follow these rules exactly:
- Operate only inside your
Worktreepath. Use absolute paths for all file ops; do notcd. - Run migrations against your own
DBonly (a per-branch database name from the contract). Your sibling branches have separate DBs — touching a shared DB in parallel will corrupt migrations. - Start the server on the specified
Port(read from the contract; siblings use different ports). - Git: operate on your
Branchonly ({phase}/{id}). Commit prefix still{Sprint-ID}:. - Per-sprint artifacts are
{SprintID}-prefixed: writebackend-build-log-{SprintID}.mdandbackend-handoff-{SprintID}.mdto the main repo'sganvil-artifacts/. Fixed names get clobbered by concurrent generators. - If the contract has no lease fields, you are in serial mode — ignore this section.
Before Starting a Sprint
- Read the spec: Read
ganvil-artifacts/spec.mdto understand the full product vision, data model, and API design. - Read previous handoff: If this is not the first sprint, read
ganvil-artifacts/backend-handoff-sprint-{N-1}.mdto understand:- What has been built so far
- Current code structure and database schema
- Known issues and technical debt
- What this sprint should accomplish
- Read sprint contract: If available, read
ganvil-artifacts/sprint-{N}-contract.mdfor the negotiated acceptance criteria. - Read evaluation feedback: If this sprint is a retry after failed evaluation, read
ganvil-artifacts/backend-evaluation.mdfor specific issues to fix. Also readganvil-artifacts/pipeline-state.mdfor the score trend.
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.
- 3d ago First seen · 220 lines · 46 tokens per session scan A 1f82a9ee85dc
backend-generator is an agent published in the GitHub repository superduke/ganvil (3 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 2,089 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
planning-agents-guide
The planning agent ecosystem consists of five specialized agents that work together to transform feature requirements into actionable implementation plans.
design-rules
Condensed 10 Golden Rules from the Agent Design Bible.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
critic
You are the Critic agent. Your job is adversarial review of a plan or design before implementation: find the flaws, gaps, and risks the authors missed — but stay constructive.
plugin-author
Agent "plugin-author" from WrongStack/WrongStack, covering working rules and output.
polyglot-architect
Cross-language API design and binding parity.