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/christopher-buss/bedrock/commitgit clone --depth 1 https://github.com/christopher-buss/bedrockWhat 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.00007 | $0.00342 |
| Opus 5 | $0.00003 | $0.00171 |
| Sonnet 5 | $0.00001 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
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 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.
What it actually says
Create a git commit following project standards
Include any of the following info if specified: $ARGUMENTS
Commit Message Rules
Follows Conventional Commits standard.
-
Format:
type(scope): description- Common types:
feat,fix,docs,refactor,test,chore,perf,style,ci - Scope: The primary package/module effected (e.g.,
cli,ocale,website). - Description: Brief summary of changes (max 72 characters), always
lowercase, no period at end. Split PascalCase with hyphens (e.g.,
Add UserAuth->add user-auth).
- Common types:
-
Content: Write clear, concise commit messages describing what changed and why. Use imperative mood (e.g., "Add feature" not "Added feature" or "Adds feature").
Process
- Run
git statusandgit diffto review changes - Run
git log --oneline -5to see recent commit style - Stage relevant files with
git add - Create commit with descriptive message
- Verify with
git status
Example
git add <files>
git commit -m "feat(open-cloud): add support for game icon uploads
This adds the ability for users to upload custom icons for their games.
Closes #123
"
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 · 46 lines · 7 tokens per session scan A b283663c6174
commit is a command published in the GitHub repository christopher-buss/bedrock (13 stars, last pushed yesterday), licensed MIT. It adds 7 tokens to every session and 342 once invoked, about $0.0000 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-09-01.
Other commands, from other repositories
sicario.verify
Run deterministic verification.
sicario.controls
Generate or update docs/compliance/control-applicability.md.
sicario.assess
Assess the repository against SicarioSpec guardrails.
sicario.review
Review the active spec, plan, tasks, staged changes, or branch for security and governance gaps.
sicario.threatmodel
Create or update docs/security/threat-model.md from the active spec and plan.
sicario.apply-findings
Convert approved SicarioSpec review findings into tasks.