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-test-pagegit 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-test-page)<a href="https://agentmods.dev/skills/cajasmota/grafel/grafel-test-page"><img src="https://agentmods.dev/badge/skills/cajasmota/grafel/grafel-test-page/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-test-page"><img src="https://agentmods.dev/badge/skills/cajasmota/grafel/grafel-test-page.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00046 | $0.02404 |
| Opus 5 | $0.00023 | $0.01202 |
| Sonnet 5 | $0.00009 | $0.00481 |
| Haiku 4.5 | $0.00005 | $0.00240 |
Grade A, and why
grafel-test-page 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 12d 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
grafel-test-page
Single-entity docgen smoke test with full emit→fill→apply roundtrip in one invocation.
This skill drives the complete grafel docgen LLM-mode loop — emit, fill (YOU are the LLM), and apply — on a single entity, in one natural-language invocation. No manual command-construction or copy-paste of paths or schema instructions required.
When to use this skill
Invoke when the user asks for any of:
- "Test docgen on
<entity>." - "Smoke-test docgen for
<entity>in group<group>." - "Iterate on docgen prose for X."
- "Run /test-docgen-page" or "/grafel-test-page" (slash commands).
- "Check the emit→fill→apply roundtrip for
<entity>."
Scope: this skill operates on ONE entity per invocation. It is designed for debugging and iteration — verifying the roundtrip, tuning guidance prose, and catching contract failures on a specific node.
For production multi-entity docgen across a full group, use the generate-docs skill instead. That skill runs Passes 0–20 across every entity in the group; this skill runs a single entity to tight iteration speed.
Inputs
Parse from the invocation text. Only prompt the user when a required field is genuinely ambiguous.
| Input | Required | Default | Notes |
|---|---|---|---|
group |
yes | — | e.g. acme, grafel, polyglot-platform |
entity |
yes | — | Prefixed ID (acme-core::<hex>), raw 16-char hex, or free-text query |
tier |
no | 1 |
0 = single-section, 1 = single-page |
section |
only when tier=0 | — | Section name from KnownSections (e.g. overview, flows) |
output-dir |
no | /tmp/docgen-test-<RFC3339-timestamp>/ |
Where emit, bundle, result, and final page land |
show-stub |
no | false |
If true, print first 30 lines of stub-page.md after emit |
Construct the RFC3339 timestamp for the default output-dir at invocation time (e.g. 2026-05-23T14:05:00Z). Never reuse a previous output-dir unless the user explicitly provides one.
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.
- 12d ago First seen · 222 lines · 46 tokens per session scan A 20e0dc65d955
grafel-test-page is a skill published in the GitHub repository cajasmota/grafel (15 stars, last pushed 3d ago), licensed MIT. It adds 46 tokens to every session and 2,404 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
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…