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/alirezarezvani/claude-code-skill-factory/ci-guardgit clone --depth 1 https://github.com/alirezarezvani/claude-code-skill-factoryWrote 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/alirezarezvani/claude-code-skill-factory/ci-guard)<a href="https://agentmods.dev/commands/alirezarezvani/claude-code-skill-factory/ci-guard"><img src="https://agentmods.dev/badge/commands/alirezarezvani/claude-code-skill-factory/ci-guard.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.00010 | $0.00188 |
| Opus 5 | $0.00005 | $0.00094 |
| Sonnet 5 | $0.00002 | $0.00038 |
| Haiku 4.5 | $0.00001 | $0.00019 |
Grade A, and why
ci-guard 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 5d 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.
What it actually says
Purpose
Run ci-commit-branch-guard.yml manually to validate branch naming and Conventional Commit syntax.
Usage
/ci-guard [ref]
ref(optional): Branch or SHA to validate. Defaults to current branch.
Steps
- Ensure you are authenticated with GitHub CLI (
gh auth status). - Determine the branch to validate (defaults to
git branch --show-current). - Trigger the workflow:
gh workflow run ci-commit-branch-guard.yml --ref ${ref:-$(git branch --show-current)} - Watch progress:
gh run watch --workflow "Commit & Branch Guard" - Resolve any failures (branch rename or commit amend) before continuing.
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.
- 5d ago First seen · 30 lines · 10 tokens per session scan A 402482e11472
ci-guard is a command published in the GitHub repository alirezarezvani/claude-code-skill-factory (855 stars, last pushed 9mo ago), licensed MIT. It adds 10 tokens to every session and 188 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
merge
You are executing the /hydra:merge command. Merge a worktree branch back into the current branch.
cm
Stage working tree changes and create a Conventional Commit (no push).
statusbar-doctor
Run cs doctor to diagnose why the status bar isn't showing what you expect.
statusbar
Show current status-bar config and list available styles + themes.
fest-commit
Commit changes with festival traceability metadata.
session-init
You are the Main Agent in an orchestrated workflow. Read and internalize these working instructions.