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.
git clone --depth 1 https://github.com/Arenukvern/skill_stewardWrote 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/arenukvern/skill_steward/faq_usage)<a href="https://agentmods.dev/rules/arenukvern/skill_steward/faq_usage"><img src="https://agentmods.dev/badge/rules/arenukvern/skill_steward/faq_usage/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/rules/arenukvern/skill_steward/faq_usage"><img src="https://agentmods.dev/badge/rules/arenukvern/skill_steward/faq_usage.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.00607 | $0.00607 |
| Opus 5.5 | $0.00243 | $0.00243 |
| Sonnet 5.5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
faq_usage 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 1mo 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
FAQ Documentation Usage Guide — Skill Steward
Q: What is DESIGN_FAQ.mdx for?
A: Explains why Guild repo decisions were made (meta-layer charter, skills vs plugins, ADRs, validation). Use when changing architecture, inclusion criteria, or documenting rationale. Path: docs/DESIGN_FAQ.mdx.
Q: What is DX_FAQ.mdx for?
A: Explains how to contribute and install (npx skills, pnpm run validate, add skill workflow). Memory Palace format. Path: docs/DX_FAQ.mdx.
Q: What is the difference from docs/decisions/ ADRs?
A: ADRs are formal decision records for significant changes. DESIGN_FAQ is a compressed index of standing why answers; link to ADRs for full deliberation.
Q: What about package-level FAQs?
A: This repo has root FAQs only. When adding sub-packages with their own boundaries, add DESIGN_FAQ.mdx + DX_FAQ.mdx there and router rows; use repository-governance-lifecycle for durable doc-lattice changes.
Q: What format should DX_FAQ.mdx use?
A: Memory Palace — emoji locations with terse code blocks (install, validate, add skill). Optimized for agent recall.
Q: Where is the charter?
A: docs/NORTH_STAR.mdx — not DESIGN_FAQ. Use repository-governance-lifecycle when changing scope or the AGENTS map.
Q: When should I reference DESIGN_FAQ.mdx?
A: Scope questions (“does this skill belong in Guild?”), plugins vs skills, documentation strategy, rejection of domain skills.
Q: When should I reference DX_FAQ.mdx?
A: Installing Guild, adding a skill, running validate, updating registry files, choosing which doc skill to use.
Q: Can I use both FAQs together?
A: Yes. Example: DESIGN explains why plugins need a separate hook install; DX shows the npx skills commands. No duplicated paragraphs.
Q: Which FAQ should I update after a change?
A: Architectural or charter why → docs/DESIGN_FAQ.mdx (+ new ADR if significant). Contributor workflow how → docs/DX_FAQ.mdx. Skill behavior → skills/{name}/SKILL.md only.
Q: Should I update FAQs when adding a skill?
A: Update docs/DX_FAQ.mdx only if the maintainer workflow changes. Update docs/DESIGN_FAQ.mdx only if the change affects repo-level why. Always update README.md, skills.sh.json, and run pnpm run validate.
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.
- 1mo ago First seen · 39 lines · 607 tokens per session scan A 2610e5b7ebc8
faq_usage is a cursor rule published in the GitHub repository Arenukvern/skill_steward (11 stars, last pushed 5d ago), licensed MIT. It adds 607 tokens to every session, about $0.0024 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-08-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .