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 cajasmota/grafel --skill grafel-resolvegit clone --depth 1 https://github.com/cajasmota/grafelWrote 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/cajasmota/grafel/grafel-resolve)<a href="https://agentmods.dev/skills/cajasmota/grafel/grafel-resolve"><img src="https://agentmods.dev/badge/skills/cajasmota/grafel/grafel-resolve/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/cajasmota/grafel/grafel-resolve"><img src="https://agentmods.dev/badge/skills/cajasmota/grafel/grafel-resolve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 Agent Snooping · line 140 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00059 | $0.02015 |
| Opus 5 | $0.00030 | $0.01007 |
| Sonnet 5 | $0.00012 | $0.00403 |
| Haiku 4.5 | $0.00006 | $0.00201 |
Grade A, and why
grafel-resolve 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 10d 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 — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grafel-resolve
Stand-alone resolution flow for ADR-0015 residual edges. Lists pending resolution candidates surfaced by grafel index, walks the user through resolutions, and submits each via the grafel_docgen_apply (kind=repairs) MCP tool. Companion to /generate-docs, but can be invoked independently when the user just wants to clean up residuals without regenerating docs.
Backward-compatibility note: The MCP tool name
grafel_docgen_apply (kind=repairs)and on-disk file namesrepair-history.json/repair-templates.jsonare preserved for backward compatibility. A separate ticket will address the API rename.
When to use this skill
Invoke it when the user asks for any of:
- "Show me grafel's residuals."
- "Help me annotate the runtime-resolved edges."
- "Run the repair flow but don't regenerate docs."
- "I have N minutes — let me chip at the bug-rate."
Run this before /grafel-tech-docs or /grafel-business-docs to ensure the graph has resolved edges. Also run as a standalone step any time you want to chip at the residual count without regenerating docs.
Do not invoke it inside /generate-docs; that flow has its own integrated resolution passes (Pass 1a, 1b, 3a). Use this skill for ad-hoc cleanup outside the doc-gen pipeline.
Inputs
- A resolved grafel group (the skill calls
grafel_orient (view=me)first). - Per-repo
<repo>/.grafel/enrichment-candidates.jsonwithkind: "repair_edge"records (emitted bygrafel indexper ADR-0015). - Optional:
~/.grafel/groups/<group>/repair-history.json(prior answers). - Optional:
~/.grafel/groups/<group>/repair-templates.json(saved templates).
If grafel_docgen_apply(kind="repairs", action=list, limit=1) returns total == 0 for every repo, the skill exits with "No residuals to resolve." after a one-line summary.
Procedure
Step 0 — Confirm scope
grafel_orient (view=me) → confirm group + repo set with the user. If the user wants a single repo, capture the slug; otherwise iterate the full group.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 149 lines · 59 tokens per session scan A 2e184149a88b
grafel-resolve is a skill published in the GitHub repository cajasmota/grafel (15 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 2,015 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.