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 skills/dryvist/claude-code-plugins/pre-commit-architecturenpx skills add dryvist/claude-code-plugins --skill pre-commit-architecturegit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWhat 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.00070 | $0.01862 |
| Opus 5 | $0.00035 | $0.00931 |
| Sonnet 5 | $0.00014 | $0.00372 |
| Haiku 4.5 | $0.00007 | $0.00186 |
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 2d 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 — 137 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) | dryvist/.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) |
dryvist/.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 |
dryvist/.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.
- 2d 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 2d ago), licensed Apache-2.0. It adds 70 tokens to every session and 1,862 once invoked, about $0.0003 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-31.
Other skills, from other repositories
rspec
This skill should be used when the user asks to "write specs", "create spec", "add RSpec tests", "fix failing spec", or mentions RSpec, describe blocks, it blocks, expect syntax, test doubles, or matchers. Should also be used when editing spec.rb files, working in spec/ directory, planning implementation phases that…
activerecord
This skill should be used when the user asks to "write a migration", "add a column", "add column to table", "create an index", "add a foreign key", "set up associations", "fix N+1 queries", "optimize queries", "add validations", "create callbacks", "use eager loading", or mentions ActiveRecord, belongsto, hasmany…
dragonruby
This skill should be used when the user asks to "create a game", "make a game", "game development", "dragonruby", "drgtk", "game loop", "tick method", "sprite rendering", "game state", or mentions args.outputs, args.state, args.inputs, coordinate system, collision detection, animation frames, or scene management.…
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…
mcp-server
This skill should be used when the user asks to "create an MCP server", "build MCP tools", "define MCP prompts", "register MCP resources", "implement Model Context Protocol", or mentions the mcp gem, MCP::Server, MCP::Tool, JSON-RPC transport, stdio transport, or streamable HTTP transport. Should also be used when…
ratatui-ruby
This skill should be used when the user asks to "create a TUI", "terminal interface", "terminal UI", "ratatui", "ratatui-ruby", "inline viewport", "full-screen terminal app", "terminal widgets", "tui.draw", "tui.pollevent", or mentions RatatuiRuby.run, managed loop, terminal rendering, Tea MVU, or building CLI…