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/release)<a href="https://agentmods.dev/commands/fatihkan/badi/release"><img src="https://agentmods.dev/badge/commands/fatihkan/badi/release.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.00686 |
| Opus 5 | $0.00000 | $0.00343 |
| Sonnet 5 | $0.00000 | $0.00137 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
release 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release notes command. Compiles changes into formats for 3 different audiences.
Badi CLI Workflow (v1.6+)
Pre-release order:
badi secret-scan --git # Verify no critical secrets
badi changelog --write --version X.Y.Z # Update CHANGELOG.md
badi commit --check # Is the last commit conventional
git tag vX.Y.Z && git push origin vX.Y.Z
gh release create vX.Y.Z --notes-file release-notes.md
This command compiles release notes tailored to 3 audiences (technical/marketing/executive).
Required Tools
- Bash (git log, git tag, diff)
- Read (commit messages, PR descriptions)
- Grep (change scan)
- Write (release note files)
Procedure (5 Steps)
Step 1: Define the Range
- Find the latest release tag:
git describe --tags --abbrev=0 - Compute the diff against the current HEAD
- Define the commit range:
git log [last-tag]..HEAD - List the affected files and modules
Step 2: Gather Data
Compile per commit:
- Commit message and description
- Related PR numbers
- Changed files and lines
- Author info
- Related issue or task numbers
Step 3: Classify the Changes
Categorize by Conventional Commits or the project's convention:
New Features (feat):
- Newly added functionality
- New API endpoints
- New UI components
Bug Fixes (fix):
- Resolved bugs
- Performance fixes
- Security patches
Breaking Changes (BREAKING):
- API changes
- Database schema changes
- Configuration changes
- Removed features
Improvements (improve):
- Performance improvements
- UX improvements
- Code quality improvements
Infrastructure (infra):
- CI/CD changes
- Dependency updates
- Documentation
Step 4: Write 3 Versions
Version A: Technical Release Notes
- The full change list by category
- Breaking changes and migration instructions
- API change details
- Known issues
- Commit hashes and PR references
Version B: Marketing Release Notes
- New features in user-focused language
- Benefit and value emphasis
- Placeholders for screenshots or visuals
- A call to action
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 · 113 lines · 0 tokens per session scan A 7801839cdc6d
release 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 686 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
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary — the complete landing pipeline.
release-notes
Generate release notes in multiple formats from git commits.
ship
Comprehensive pre-deployment verification to ensure release readiness.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.
plan-execute
Execute a validated plan: worktree isolation, TDD scaffolding, level-based parallel agents, quality gate with smoke test, PR creation and merge. Handles everything through to merged PR.
pr
Analyze changes, detect scope issues, and create a well-structured PR.