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 frap129/opencode-rules --skill crafting-rulesgit clone --depth 1 https://github.com/frap129/opencode-rulesWrote 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/frap129/opencode-rules/crafting-rules)<a href="https://agentmods.dev/skills/frap129/opencode-rules/crafting-rules"><img src="https://agentmods.dev/badge/skills/frap129/opencode-rules/crafting-rules/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/frap129/opencode-rules/crafting-rules"><img src="https://agentmods.dev/badge/skills/frap129/opencode-rules/crafting-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium System Prompt Leakage · line 3 Skill contains patterns that could indirectly extract system prompts through rephrasing, translation, summarization, or side-channel techniques.Fix: Guard against indirect extraction by refusing to summarize, translate, or rephrase system instructions. Add explicit anti-extraction clauses.
- medium Rogue Agent · line 56 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00058 | $0.02224 |
| Opus 5.5 | $0.00023 | $0.00890 |
| Sonnet 5.5 | $0.00012 | $0.00445 |
| Haiku 4.5 | $0.00006 | $0.00222 |
Grade A, and why
crafting-rules 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crafting Rules
Overview
Rules are markdown files with optional YAML frontmatter, injected into the system prompt to guide agent behavior. Scope them with filters or leave unconditional for global standards.
Field Reference
| Field | Type | Category | Purpose |
|---|---|---|---|
globs |
string[] |
Legacy | Apply when any observed file's path matches a pattern |
fileContains |
string | string[] |
Legacy | Apply when an observed file's text contains a literal substring |
keywords |
string[] |
Legacy | Apply when the user's latest prompt matches a keyword |
tools |
string[] |
Legacy | Apply when any listed tool ID is available |
model |
string[] |
Runtime | Match against the current LLM model ID |
agent |
string[] |
Runtime | Match against the current agent type (e.g., programmer) |
command |
string[] |
Runtime | Match against the current slash command (e.g., /plan) |
project |
string[] |
Runtime | Match against detected project tags (e.g., node, rust) |
branch |
string[] |
Runtime | Match against git branch name (supports glob patterns) |
os |
string[] |
Runtime | Match against OS (linux, darwin, win32) |
ci |
boolean |
Runtime | Match against CI environment (true = in CI) |
match |
'any' | 'all' |
Combinator | any (default): OR logic. all: AND logic. |
- All fields are optional; no frontmatter means the rule always applies.
- With
match: any(default), the rule applies if ANY declared condition matches. - With
match: all, the rule applies only if ALL declared conditions match. globsandfileContainsform one file-observation family: when both are declared, the same observed file must satisfy both. The family counts as one condition in the algebra.- File observations come only from successful live Read, Write, Edit, Apply Patch, and path-associated LSP tool events. Grep, Glob, shell, custom/MCP tools, message prose, and historical tool events contribute nothing to
globs/fileContains. - A durable rule first matched by a live file observation takes effect at that earliest dispatch — not on the next user message.
- When a runtime value is unavailable (e.g., no git repo), that dimension is a non-match.
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 · 221 lines · 58 tokens per session scan A adf32cd2b1b5
crafting-rules is a skill published in the GitHub repository frap129/opencode-rules (119 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 2,224 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-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…