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/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/conventional-commit)<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/conventional-commit"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/conventional-commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/saajunaid/caddis-plugin/conventional-commit"><img src="https://agentmods.dev/badge/commands/saajunaid/caddis-plugin/conventional-commit.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.01326 |
| Opus 5.5 | $0.00005 | $0.00530 |
| Sonnet 5.5 | $0.00002 | $0.00265 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
conventional-commit 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 1mo 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/commit - Conventional Commit
Generate and optionally execute a conventional commit for staged or unstaged changes.
Automated Workflow
When invoked, follow these steps:
- Run
git statusto review changed files - Run
git diff --cached(orgit diffif nothing staged) to inspect changes - Analyze the changes and construct a commit message using the format below
- Present the commit message to the user for confirmation
- Execute:
git commit -m "<message>"
Commit Message Format
## Conventional Commits Format
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
## Types (required)
| Type | Description | Example |
|------|-------------|---------|
| feat | New feature | `feat: add user authentication` |
| fix | Bug fix | `fix: resolve login timeout issue` |
| docs | Documentation only | `docs: update API reference` |
| style | Formatting, no code change | `style: fix indentation in models.py` |
| refactor | Code change, no feature/fix | `refactor: simplify database queries` |
| perf | Performance improvement | `perf: optimize image loading` |
| test | Adding/fixing tests | `test: add unit tests for auth module` |
| build | Build system changes | `build: update requirements.txt` |
| ci | CI configuration | `ci: add GitHub Actions workflow` |
| chore | Other maintenance | `chore: update .gitignore` |
| revert | Revert previous commit | `revert: revert "feat: add feature"` |
## Scopes (optional)
Indicate the section of codebase:
- `feat(api)`: Feature in API module
- `fix(ui)`: Fix in UI module
- `docs(readme)`: Documentation in README
Common scopes (adapt to your project):
- `api` - Backend/API layer
- `ui` - Frontend/UI layer
- `db` - Database/SQL
- `auth` - Authentication
- `config` - Configuration
- `lib` - Shared libraries
## Breaking Changes
Use `!` or `BREAKING CHANGE:` footer:
feat(api)!: change authentication flow
BREAKING CHANGE: JWT tokens now expire after 1 hour
## Examples
### Simple Feature
feat(ui): add network dashboard page
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.
- 1mo ago First seen · 236 lines · 12 tokens per session scan A 7b4858ec4869
conventional-commit is a command published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,326 once invoked, about $0.0000 per session on Opus 5.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-09.
Other commands, from other repositories
commit
Based on the above changes, create a single git commit.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.