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 commands/fatihkan/badi/briefgit 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/brief)<a href="https://agentmods.dev/commands/fatihkan/badi/brief"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/brief.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.00000 | $0.00800 |
| Opus 5 | $0.00000 | $0.00400 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
brief 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project briefing command. Turns raw project ideas into structured, actionable briefs.
Required Tools
- Read (existing project info)
- Write (brief file)
- Grep (similar project search)
- Glob (resource scan)
Procedure (7 Steps)
Step 1: Capture the Idea
Collect from the user (accept it even unstructured):
- Problem: What problem are we solving?
- Solution: How do we plan to solve it?
- Users: Who will use it? (primary and secondary audience)
- Success Criterion: How will we measure success?
- Motivation: Why now? What triggered it?
However raw the idea, convert it into a structured format.
Step 2: Define the Scope
Draw clear lines:
In Scope:
- Features delivered in phase one
- Core user flows
- Minimum technical requirements
Out of Scope:
- Features deliberately excluded
- Work deferred to future phases
- Responsibility boundaries
Assumptions:
- Technical assumptions (infrastructure, access, etc.)
- Business assumptions (budget, time, resources)
- User assumptions (skill level, access, etc.)
Step 3: User Stories (MoSCoW)
Write 5-10 user stories, each with:
- Format: "As a [role], I want [goal], so that [benefit]."
- Acceptance criteria (2-4 items)
- MoSCoW priority:
- Must: The product cannot work without it
- Should: Important but can miss the first release
- Could: Nice to have, not a priority
- Won't: Deliberately not done in this phase
Step 4: Technical Assessment
- Tech Stack: Suggested languages, frameworks, tools
- Integrations: Third-party services and APIs
- Data Requirements: Database, storage, data flow
- Infrastructure: Hosting, CI/CD, monitoring
- Constraints: Performance requirements, compliance, scale
- Technical Debt Risk: Known shortcuts or workarounds
- Build vs Buy Analysis: Which components to build, which to use off the shelf?
Step 5: Risk Identification
Build a risk matrix:
| Risk | Likelihood (1-5) | Impact (1-5) | Risk Score | Mitigation Strategy |
|---|---|---|---|---|
| [risk description] | [value] | [value] | [LxI] | [strategy] |
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 · 108 lines · 0 tokens per session scan A 7b0de368dadf
brief is a command published in the GitHub repository fatihkan/badi (7 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 800 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-08-31.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
sonarqube
Analyze SonarCloud quality issues for a specific PR.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
scaffold
Interactive coach that asks 4-5 questions to determine whether you need an agent, command, skill, hook, or rule — then generates a ready-to-use template. Usage: /scaffold (no arguments — starts the coaching session).
investigate
Systematic root-cause debugging — find the cause before writing any fix.