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 dryvist/claude-code-plugins --skill pre-commit-architecturegit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/pre-commit-architecture)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/pre-commit-architecture"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/pre-commit-architecture/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/dryvist/claude-code-plugins/pre-commit-architecture"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/pre-commit-architecture.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.00059 | $0.01946 |
| Opus 5.5 | $0.00024 | $0.00778 |
| Sonnet 5.5 | $0.00012 | $0.00389 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
pre-commit-architecture 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 yesterday.
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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Commit Architecture
Single canonical home per artifact. No per-repo duplication of hook definitions or shared lint configs.
| Artifact | Canonical home | How consumers pull it |
|---|---|---|
| Pre-commit hook definitions (Nix consumers) | dryvist/nix-devenv — lib/pre-commit-hooks.nix + flake-modules/profiles/<name>.nix |
imports = [ inputs.nix-devenv.flakeModules.<profile> ] in the consumer's flake.nix |
| Pre-commit hook definitions (non-Nix consumers) | JacobPEvans/.github precommit/templates/<profile>.yaml |
Copy at scaffold; Renovate keeps rev: pins fresh |
Shared lint configs (.markdownlint-cli2.yaml, .tflint.hcl, .ansible-lint, .yamllint.yml) |
JacobPEvans/.github — .markdownlint-cli2.yaml at root for backward compat; the rest in precommit/configs/ |
Nix path: nix-devenv.lib.fetch-shared-configs materializes nix-store paths; non-Nix path: copy at scaffold |
zizmor.yml workflow-security policy |
JacobPEvans/.github at the root |
Same as above — passed as --config by the base profile's zizmor hook |
Profiles
nix-devenv exports six profile names. Pick one per consumer repo.
| Profile | Adds on top of base hygiene | Inventory match |
|---|---|---|
base |
Nothing — exposes the base wiring (deadnix, statix, check-yaml/toml/json, check-merge-conflict, check-added-large-files=500k, end-of-file-fixer, trim-trailing-whitespace, detect-private-keys, markdownlint-cli2, zizmor, treefmt) | Generic repos |
nix |
Alias for base (deadnix and statix file-glob to .nix automatically) |
nix-* repos |
markdown |
Alias for base (markdownlint-cli2 file-globs to .md automatically) |
Markdown-heavy repos |
terraform |
terraform-format, terraform-validate, tflint |
terraform-*, tofu-* |
ansible |
ansible-lint, yamllint |
ansible-* |
python |
ruff, ruff-format, mypy |
python-template, mlx-benchmarks, etc. |
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.
- yesterday Changed 894b6e4a07bb
- 8d ago Changed · +3 lines 3363b4062f06
- 25d ago Changed · -11 tokens per session 1b8f229bd5f8
- 1mo ago First seen · 137 lines · 70 tokens per session scan A 8870c3bb09a1
pre-commit-architecture is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 59 tokens to every session and 1,946 once invoked, about $0.0002 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-31.
Other skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
auto-claude
Autonomous multi-agent coding with git worktree isolation, QA validation, and memory. Use for complex features requiring autonomous implementation.
github-ops
GitHub remote operations and README authoring: repo creation, metadata, releases, issue/PR management with preview-before-send, README as a landing page (badge row, features-as-benefits, screenshots, Recent Updates), and read-only security auditing. Triggers on: write a README, improve the README, README badges…