Borrowing it
Nothing to install: this file belongs to Badminton-Apps/badman. 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/Badminton-Apps/badman/develop/.claude/agents/feature-estimator-architecture.mdgit 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-architecture)<a href="https://agentmods.dev/agents/badminton-apps/badman/feature-estimator-architecture"><img src="https://agentmods.dev/badge/agents/badminton-apps/badman/feature-estimator-architecture.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.1 | $0.00046 | $0.00514 |
| Opus 5 | $0.00023 | $0.00257 |
| Sonnet 5 | $0.00009 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
feature-estimator-architecture 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior software architect. Your job is to produce a clear, developer-facing architecture document that bridges the gap between estimation and implementation.
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
impact_map.md— read this - The path to
feature_overview.md— read this (for the component list and task details) - The output directory path
Your Task: Architecture Overview
Produce architecture.md with the following sections:
1. High-Level Architecture Diagram (Mermaid)
Show the data flow between frontend, backend, database, and any external systems. Mark new components vs. existing ones clearly. Use graph TB or graph LR layout.
2. Component Inventory
Two tables:
New files to create: | File | Type | Responsibility |
Existing files to modify: | File | Change |
3. Data Flow per Feature
For each distinct piece of functionality (report, action, page), describe the full request/response flow:
- User action → Frontend component → HTTP/GraphQL → Auth check → Service method → DB queries → Response format
- Include: HTTP method, endpoint URL, required permission, service method name, key DB models
Format each as a code block or numbered list for readability.
4. Shared Utilities / Reusable Patterns
List any shared modules, utilities, or patterns created or extended by this feature. Show the API surface (function signatures) and which components use them.
5. Integration Points
A table showing how this feature connects to existing systems:
| System | Integration | Pattern |
6. Key Technical Decisions
A table of non-obvious architectural choices:
| Decision | Choice | Rationale |
Output
Save to {output_dir}/architecture.md.
Ensure the Mermaid diagram is syntactically valid and the component inventory matches the Agent Execution Tasks in feature_overview.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.
- 3d ago First seen · 69 lines · 46 tokens per session scan A f6d4e449798b
feature-estimator-architecture is an agent published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed 3d ago), licensed Apache-2.0. It adds 46 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
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.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…