Borrowing it
Nothing to install: this file belongs to AsiaOstrich/EngramGraph. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/AsiaOstrich/EngramGraph/main/.agents/skills/skill-builder/SKILL.mdgit clone --depth 1 https://github.com/AsiaOstrich/EngramGraphWrote 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/asiaostrich/engramgraph/skill-builder)<a href="https://agentmods.dev/skills/asiaostrich/engramgraph/skill-builder"><img src="https://agentmods.dev/badge/skills/asiaostrich/engramgraph/skill-builder/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/asiaostrich/engramgraph/skill-builder"><img src="https://agentmods.dev/badge/skills/asiaostrich/engramgraph/skill-builder.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.00115 | $0.01353 |
| Opus 5.5 | $0.00046 | $0.00541 |
| Sonnet 5.5 | $0.00023 | $0.00271 |
| Haiku 4.5 | $0.00012 | $0.00135 |
Grade A, and why
skill-builder 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 14d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Process-to-Skill Assistant
Guides you from "I keep doing this manually" to a properly built Skill, with the right amount of process along the way.
When to Use
- You've done the same multi-step sequence ≥ 3 times manually
- A teammate asks "how do we do X again?" for the 3rd time
- You built a Skill ad-hoc and want to formalize it
Core Principle
A Skill records process knowledge. Memory records historical facts. When you notice yourself executing the same steps repeatedly, that's a Skill candidate.
Decision Tree
New Skill needed?
├── Modifying existing Skill?
│ → Delta path: append ## MODIFIED / ## ADDED to existing SKILL.md
│ update version field → done
│
├── Answer these 4 questions (any "yes" → Complex):
│ 1. More than 7 steps?
│ 2. Branching logic between steps (if/else)?
│ 3. Requires knowledge from 3+ separate standards/decisions?
│ 4. Output directly affects sub-project source code?
│
├── All "no" → Simple path
│ → Fill Skill Brief (templates/SKILL-BRIEF-TEMPLATE.md)
│ → Create SKILL.md directly (no XSPEC needed)
│
└── Any "yes" → Complex path
→ Create XSPEC first → run /sdd
→ Return here after XSPEC Approved
Deprecating a Skill?
→ Add to SKILL.md frontmatter:
status: deprecated
deprecated_at: YYYY-MM-DD
deprecated_reason: "..."
superseded_by: "/new-skill" (if applicable)
→ Mark archived in SKILL-CANDIDATES.md
Placement Decision
Before creating SKILL.md, decide where it belongs:
| Condition | Placement |
|---|---|
| Steps reference project-specific paths (e.g. TECH-RADAR.md, DEC-*.md) | Project: {project}/.claude/skills/ |
| Steps are universal (no project-specific paths) | UDS: skills/{name}/ + zh-TW locale |
Workflow
Step 1 — Describe the Process
Capture the repeated sequence:
- What steps, in what order?
- How many times done manually so far?
- What tools or files does it touch?
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.
- 14d ago First seen · 148 lines · 115 tokens per session scan A 4449b2b78e79
skill-builder is a skill published in the GitHub repository AsiaOstrich/EngramGraph (3 stars, last pushed today), licensed MIT. It adds 115 tokens to every session and 1,353 once invoked, about $0.0005 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-10-16.
Other skills, from other repositories
kivgraph
Use Kivgraph's local MCP server to search symbols, read their source, and follow references, dependencies, cross-repository consumers and graph status in the indexed code graph.
mushroom
Live graph memory for agents — query and create entities, derive relationships by rule, explain why two things are associated, read the graph at a past commit, ask what a change would do, and answer as one role. Trigger on: memory, remember, recall, relationship, entity, association, why are X and Y related, as of…
omnigraph
Operate OmniGraph graphs and deployments. Use for .pg schemas, .gq queries, OmniGraph CLI commands, file:///s3:///az:// graph URIs, cluster.yaml, operator config, bearer-authenticated servers, graph-backed knowledge or memory, Blob values, embeddings, branches, commits, and change feeds. Apply especially before schema…
code-graph
This skill should be used when understanding code structure, finding dependencies between functions/classes, tracing call graphs, or exploring code relationships. Trigger phrases include 'code graph', 'call graph', 'who calls', 'what calls', 'find dependencies', 'code structure', 'inheritance', 'find paths'.
usage
Query LeanKG knowledge graph for code understanding. Use when exploring a codebase, finding functions, tracing dependencies, or calculating impact radius.
codestory-grounding
Use when discovering repository structure, tracing relationships, analyzing change impact, or validating CodeStory retrieval or an installed plugin through the CodeStory plugin MCP. Skip only for bounded inspection or editing of named files that does not require those operations.