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/chan4lk/specclaw/patternsnpx skills add chan4lk/specclaw --skill patternsgit clone --depth 1 https://github.com/chan4lk/specclawWrote 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/chan4lk/specclaw/patterns)<a href="https://agentmods.dev/skills/chan4lk/specclaw/patterns"><img src="https://agentmods.dev/badge/skills/chan4lk/specclaw/patterns.svg" alt="Measured on agentmods" 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 | $0.00039 | $0.00357 |
| Opus 5 | $0.00019 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00071 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
patterns 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 4d 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.
What it actually says
specclaw patterns
First, run specclaw-ensure-init .specclaw — idempotently creates .specclaw/ if it doesn't exist (silent if already initialized; auto-inits using the current directory's basename as the project name).
Track recurring patterns across changes — errors and learnings that repeat become prevention rules.
Scan a change for patterns:
specclaw-detect-patterns .specclaw scan <change>
Reads errors.md and learnings.md, matches against existing patterns, creates new ones or increments existing.
List all patterns:
specclaw-detect-patterns .specclaw list [--min-recurrence N]
Promote a pattern to the repo-local knowledge base:
specclaw-detect-patterns .specclaw promote <pat-id>
Promote writes the prevention rule to .specclaw/knowledge/agent-hints.md — never to the plugin itself. The plugin stays versioned and generic; each repo builds its own knowledge over time.
Auto-promotion: patterns with 3+ occurrences are flagged ⚠️ — run promote to write their prevention rules into the local knowledge base so future build agents see them automatically.
Pattern registry lives at .specclaw/patterns.md (global, not per-change).
Knowledge base lives at .specclaw/knowledge/ (repo-local, not plugin).
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.
- 4d ago First seen · 33 lines · 39 tokens per session scan A e663c66554ec
patterns is a skill published in the GitHub repository chan4lk/specclaw (12 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 357 once invoked, about $0.0002 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-30.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
agui-dotnet-streaming-chat
Get started with the AG-UI .NET SDK: bootstrap and run your first streaming-chat app (client + server) with the AG-UI .NET NuGet packages (AGUI.Client, AGUI.Server, AGUI.Formatting, AGUI.Abstractions). USE FOR: which packages to install and how to wire them; constructing an AGUIChatClient against an endpoint and…
agui-dotnet-sample-step
Add a GettingStarted sample Step (a Server/Client pair) to the AG-UI .NET SDK that demonstrates one protocol feature the way we want users to write it. USE FOR: adding a new samples/GettingStarted/StepNN Server+Client pair, wiring it into AGUI.slnx and the integration-test project, giving it a deterministic…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…