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/pchalasani/claude-code-tools/add-patternnpx skills add pchalasani/claude-code-tools --skill add-patterngit clone --depth 1 https://github.com/pchalasani/claude-code-toolsWhat 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.00056 | $0.00228 |
| Opus 5 | $0.00028 | $0.00114 |
| Sonnet 5 | $0.00011 | $0.00046 |
| Haiku 4.5 | $0.00006 | $0.00023 |
Grade A, and why
add-pattern 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.
This is a copy
100% identical to add-pattern — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
add-pattern
Instructions
When you learn a new Langroid design pattern, do the following:
-
Add an entry in the sibling
patterns/SKILL.mdfile in the appropriate category section, containing a DESCRIPTION of the goal of the pattern (i.e. what it enables you to implement), accompanied by a- Reference:pointer to a markdown DOCUMENT in thepatterns/directory.IMPORTANT - The DESCRIPTION should be clear enough that future YOU can effectively use it to MATCH design problems you may encounter in future.
-
In that DOCUMENT, describe the idea of the implementation along with code examples. Follow the format of existing pattern files (Problem, Solution, Complete Code Example, Key Points, When to Use).
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 First seen · 26 lines · 56 tokens per session scan A b0d3c7f7f359
add-pattern is a skill published in the GitHub repository pchalasani/claude-code-tools (1,986 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 228 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to add-pattern, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
bro
Restate the last message in plain human language, with no jargon.
database-engineer
SQLite database expertise for migrations, multi-tenant patterns, transactional safety, FTS5 virtual tables, and schema evolution. Use this skill for ANY work involving schema changes, data migrations, INSERT/UPSERT semantics, FTS5 rebuilds, transaction rollback design, multi-tenant data isolation, or SQLite…
monitoring-specialist
System monitoring, alerting, and observability implementation.
panel
Multi-provider deliberation panel for COMPLEX, multi-view questions — architecture, strategy, market research, and codebase sweeps. Runs a 4-stage deliberation across the provider fleet (diverge → contrarian red-team → adversarial verify → cited synthesis), the same multi-perspective rigour the plan-gate already…
t0-orchestrator
Master orchestration for the VNX multi-terminal system. Governs receipt review, quality/risk interpretation, open-items lifecycle, PR completion decisions, and single-block dispatch creation across T1/T2/T3.