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 agentmods add rules/guorunjie/skillpack-forge/docs-ops-demogit clone --depth 1 https://github.com/guorunjie/skillpack-forgeWrote 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/rules/guorunjie/skillpack-forge/docs-ops-demo)<a href="https://agentmods.dev/rules/guorunjie/skillpack-forge/docs-ops-demo"><img src="https://agentmods.dev/badge/rules/guorunjie/skillpack-forge/docs-ops-demo.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 | $0.00126 | $0.00126 |
| Opus 5 | $0.00063 | $0.00063 |
| Sonnet 5 | $0.00025 | $0.00025 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
docs-ops-demo 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 3d 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.
What it actually says
docs-ops-demo
Generated from skillpack.yaml by Skillpack Forge.
Documentation automation workflows for keeping project docs current.
Principles
- Prefer source-of-truth files over stale summaries
- Keep generated documentation concise and easy to review
- Link commands, files, and examples that readers can verify
Commands
- install:
npm install - test:
npm test - docs:
npm run docs - docs:check:
npm run docs:check
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.
- 3d ago First seen · 24 lines · 126 tokens per session scan A 5c0d43405196
docs-ops-demo is a cursor rule published in the GitHub repository guorunjie/skillpack-forge (1 stars, last pushed 3mo ago), licensed MIT. It adds 126 tokens to every session, about $0.0006 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-31.
Other cursor rules, from other repositories
project
Glitch Payment Gateway project coding guidelines — WooCommerce payment plugin conventions, stack, folder structure, dev commands.
doc-sync
Documentation sync rules — which docs to update when code changes in src/.
commit
Commit rules — branch safety, explicit staging, 3-option commit messages, push approval.
agent-observations
Mandatory agent observation logging — anomalies, recommendations, and critical findings must be disclosed before commit.
devtools
Browser DevTools and local development access — dev server, credentials, viewport rules.
agent-context-doctor
Agent Context Doctor project rule adapter.