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 skills add DavidROliverBA/ArchitectKB --skill commitgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/skills/davidroliverba/architectkb/commit)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/commit"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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/skills/davidroliverba/architectkb/commit"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/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.00013 | $0.00657 |
| Opus 5.5 | $0.00005 | $0.00263 |
| Sonnet 5.5 | $0.00003 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00066 |
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 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit Vault Changes
Stage and commit changes to the vault with properly formatted UK English conventional commit messages.
Usage
/commit # Auto-detect changes and commit
/commit -m "message" # Commit with a specific message
/commit --amend # Amend the previous commit (use sparingly)
Workflow
1. Review Changes
git status
git diff --stat
2. Stage Changes
Stage specific files rather than using git add -A:
- Never stage:
.env, credentials,.secrets.baseline(unless updated by detect-secrets) - Use
git add -ufor modified/deleted files with Unicode filenames (avoids octal encoding issues) - Use
git lfs trackfirst for large binary files (PPTX, PDF >100MB)
3. Compose Commit Message
Follow these conventions:
- UK English spelling (e.g., "organise", "summarise", "colour")
- Imperative mood in subject line (e.g., "Add meeting note" not "Added meeting note")
- Subject line under 72 characters
- Body explains the "why" not the "what" (the diff shows the what)
- Always include the co-author tag
4. Commit Format
<type>: <subject>
<optional body>
Co-Authored-By: Claude Opus 4.6 <[email protected]>
Types:
| Type | When to Use |
|---|---|
Add |
New notes, skills, scripts, templates |
Update |
Enhancements to existing notes or config |
Fix |
Bug fixes, broken links, frontmatter errors |
Refactor |
Restructuring without changing meaning |
Archive |
Moving notes to Archive/ |
Remove |
Deleting deprecated content |
Docs |
Documentation-only changes (CLAUDE.md, READMEs) |
5. Pre-commit Checks
The vault has pre-commit hooks that may:
- Run
detect-secrets(may need.secrets.baselineupdate) - Check for large files (use git LFS for >100MB)
- Fix trailing whitespace and EOF
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 · 87 lines · 13 tokens per session scan A b257c78dbb8a
commit is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (53 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 657 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.