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 using-grafelgit 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/using-grafel)<a href="https://agentmods.dev/skills/cajasmota/grafel/using-grafel"><img src="https://agentmods.dev/badge/skills/cajasmota/grafel/using-grafel.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.1 | $0.00049 | $0.02921 |
| Opus 5 | $0.00024 | $0.01460 |
| Sonnet 5 | $0.00010 | $0.00584 |
| Haiku 4.5 | $0.00005 | $0.00292 |
Grade A, and why
using-grafel 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 7d 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 — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
using-grafel
A practical routing guide for AI agents in a grafel-registered codebase.
grafel exposes 22 intent-named tools. Each one collapses a family of
related operations under a single verb with a discriminator parameter
(kind / direction / aspect / detail / action / scope). Pick the
tool by intent, then pick the discriminator value for the specific
question.
The single biggest win: stop reasoning over raw source by hand. When the
question is "are these two things different?", "what's affected?", "what
calls this?", or "what flows through here?", there is a dedicated tool that
answers it structurally. Reaching for grafel_get_source + manual reading is
the slow, error-prone path.
1. Intent → tool map
Comparison & analysis (reach here FIRST)
| Your intent | Tool + discriminator |
|---|---|
| Compare reference vs candidate response shape | grafel_diff aspect=response_shape — not get_source + eyeball |
| Compare request payloads between two refs | grafel_diff aspect=payload |
| Compare auth posture between two refs | grafel_diff aspect=auth |
| Compare constant/literal parity between two refs | grafel_diff aspect=literals |
| Compare arbitrary entity sets between two refs | grafel_diff aspect=refs |
| What's affected if I change X (one entity) | grafel_impact_radius scope=entity |
| What's affected by this changeset / PR | grafel_impact_radius scope=changeset |
| Tech-debt: dead code | grafel_debt kind=dead_code |
| Tech-debt: import/dependency cycles | grafel_debt kind=cycles |
| Tech-debt: stub / unimplemented functions | grafel_debt kind=stubs |
| Tech-debt: impure functions | grafel_debt kind=impure |
| License audit | grafel_debt kind=license |
| Security findings | grafel_security kind=findings |
| Hardcoded secrets | grafel_security kind=secrets |
| Auth coverage across endpoints | grafel_security kind=auth_coverage |
| Test coverage | grafel_test_analysis kind=coverage |
| Test reachability | grafel_test_analysis kind=reachability |
| Contract-test effectiveness | grafel_test_analysis kind=contract_effectiveness |
| Recurring code patterns | grafel_patterns kind=code |
| Recurring graph patterns | grafel_patterns kind=graph |
| Template patterns | grafel_patterns kind=template |
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.
- 7d ago First seen · 308 lines · 49 tokens per session scan A c56d14bbf0de
using-grafel is a skill published in the GitHub repository cajasmota/grafel (12 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 2,921 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…