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/fatihkan/badiWrote 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/commands/fatihkan/badi/proposal)<a href="https://agentmods.dev/commands/fatihkan/badi/proposal"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/proposal.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.00000 | $0.00970 |
| Opus 5 | $0.00000 | $0.00485 |
| Sonnet 5 | $0.00000 | $0.00194 |
| Haiku 4.5 | $0.00000 | $0.00097 |
Grade A, and why
proposal 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.
How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Client proposal command. Builds a professional client proposal from project summaries. Valid for 30 days.
Required Tools
- Read (project data, existing brief)
- Write (proposal file)
- Grep (similar proposal search)
Procedure (6 Steps)
Step 1: Overview
Get from the user:
- Client Name: Company or person
- Needs: The problems and requests the client stated
- Desired Outcomes: Success criteria and expectations
- Constraints: Budget range, time limits, technical boundaries
- Decision Maker: Who approves? Technical or business?
- Competition: Are other proposals being evaluated?
If an existing brief exists (in briefs/), build on it.
Step 2: Define the Scope
Split the deliverables into phases:
Phase 1: [name]
- Deliverables: [detailed list]
- Expected outputs: [concrete results]
- Duration: [estimate]
- Dependencies: [prerequisites]
Phase 2: [name]
- ...
For each phase:
- Assumptions (what will be provided, what is expected)
- Out-of-scope items (state explicitly)
- Acceptance criteria
Step 3: Timeline
Map the phases to calendar weeks:
| Week | Phase | Deliverables | Milestone |
|---|---|---|---|
| 1-2 | Research & Design | ... | Design Approval |
| 3-5 | Development | ... | MVP Demo |
| 6 | Test & Polish | ... | QA Approval |
| 7 | Launch & Support | ... | Go-Live |
- Leave a 2-3 day review buffer between phases
- Mark milestones explicitly
- Note the critical path
Step 4: Pricing (2 Options)
Option A: Full Scope (Recommended)
| Item | Unit | Quantity | Unit Price | Total |
|---|---|---|---|---|
| ... | ... | ... | ... | ... |
- Subtotal: [amount]
- VAT: [amount]
- Grand Total: [amount]
Option B: MVP / Reduced Scope
| Item | Unit | Quantity | Unit Price | Total |
|---|---|---|---|---|
| ... | ... | ... | ... | ... |
- Grand Total: [amount]
Optional Add-on Services:
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 · 147 lines · 0 tokens per session scan A 7a1edb11689a
proposal is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 970 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-09-06.
Other commands, from other repositories
plan-start
5-phase planning command: PRD analysis, design review, technical decisions, dynamic research team, metrics. Produces a complete implementation plan + ADRs before any code is written.
plan-ceo-review
Strategic product gate — challenge the brief, find the 10-star product hiding inside the request, before writing any code.
routines-discover
Analyzes the current project to surface high-value Routines use cases across the three trigger types (schedule, API, GitHub events). Usage: /routines-discover.
check-cache-bugs
Audit Claude Code setup for cache bugs (CC#40524) — sentinel, --resume/--continue, attribution header + ArkNill B3/B4/B5.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.