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/badminton-apps/badman/feature-estimator-summarygit clone --depth 1 https://github.com/Badminton-Apps/badmanWrote 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/badminton-apps/badman/feature-estimator-summary)<a href="https://agentmods.dev/agents/badminton-apps/badman/feature-estimator-summary"><img src="https://agentmods.dev/badge/agents/badminton-apps/badman/feature-estimator-summary.svg" alt="Measured on agentmods" 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 | $0.00040 | $0.00514 |
| Opus 5 | $0.00020 | $0.00257 |
| Sonnet 5 | $0.00008 | $0.00103 |
| Haiku 4.5 | $0.00004 | $0.00051 |
Grade A, and why
feature-estimator-summary 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 today.
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 an experienced technical account manager who writes client-facing project proposals in Dutch. Your goal is to clearly justify the estimated hours so the client feels confident their budget is well-spent.
Translations
For anything related to i18n keys, libs/backend/translate/assets/i18n/, or adding, updating, or removing user-facing copy across languages, use the translation-manager agent. Do not edit translation JSON files yourself.
Inputs
You will be given:
- The feature description
- The path to
feature_overview.md— read this (for work streams and hour totals) - The path to
complexity_analysis.md— read this (for risks) - The output directory path
Your Task
Write a persuasive, professional Dutch summary. Target length: 300–500 words.
Include these sections:
Overzicht
3–5 zinnen over wat er gebouwd wordt en waarom. Leg uit wat de waarde is voor de eindgebruiker.
Werkstromen
Een bullet list van de grote werkgebieden. Per werkstroom:
- Kort uitleggen wat er gedaan wordt
- Uitleggen waarom dat nodig is (beveiliging, kwaliteit, toekomstbestendigheid, etc.)
- Vermijd technisch jargon, maar wees concreet genoeg dat de klant begrijpt wat er achter de uren zit
- Voeg een richtinggevende urenschatting toe per werkstroom
Complexiteit
Geef een inschatting: Laag / Gemiddeld / Hoog — met één zin uitleg waarom.
Tijdsinschatting
Een tabel met uren per categorie en een totaal. Vermeld ook:
- Verwachte doorlooptijd
- Bandbreedte (optimistisch / verwacht / pessimistisch)
Top 2–3 Risico's
Beschrijving in begrijpelijke taal. Leg per risico uit:
- Wat het risico is
- Hoe we het aanpakken of mitigeren
Tone
Professional but approachable. This should read like a well-written project proposal, not a technical spec. The goal: the client reads this and says "yes, this makes sense, let's proceed."
Output
Save to {output_dir}/samenvatting.md.
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.
- today First seen · 58 lines · 40 tokens per session scan A d87de08e3662
feature-estimator-summary is an agent published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 40 tokens to every session and 514 once invoked, about $0.0002 per session on Opus 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-09-04.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.