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/granoflow/granoflow-mcp-server/skill-testinggit clone --depth 1 https://github.com/granoflow/granoflow-mcp-serverWhat 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.00383 | $0.00383 |
| Opus 5 | $0.00192 | $0.00192 |
| Sonnet 5 | $0.00077 | $0.00077 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
skill-testing 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 yesterday.
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
Skill Testing
Follow popular Agent Skills practice (Anthropic / agentskills.io style):
Allowed in CI
- Structure:
SKILL.mdexists; YAML frontmatter has non-emptynameanddescription;namematches the skill directory;descriptionlength ≤ 1024. Covered bytests/skills-structure.test.ts. - Scripts: unit/integration tests for real
skills/*/scriptsI/O and error codes undertests/python/. - MCP surface: skill tools assert
ok,data.path, non-emptyskill(optionally starts with---), and optionalreferences[].referenceIdpresence — not body phrases.
Forbidden
Do not add or restore tests that treat skill markdown as a snapshot:
// FORBIDDEN — prose / gate-copy contract locks
const skill = readFileSync("skills/granoflow-…/SKILL.md", "utf8");
expect(skill).toContain("some workflow sentence");
expect(reference).toMatch(/hard.gate.phrase/i);
expect(JSON.stringify(skillToolResult)).toContain("activation phrase");
That pattern does not prove agent behavior; it only freezes wording and creates false confidence.
Behavior correctness
Use LLM evals (trigger + functional expectations) when validating that agents follow a skill. This repo does not require eval harness in CI today. Do not substitute evals with markdown toContain locks.
Planning / ask-mode
Do not invent natural-language Excel “test cases” for prose-only skill edits.
For those changes: files + intent → edit → npm run check. See change-quality-gate.mdc.
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.
- yesterday First seen · 38 lines · 383 tokens per session scan A ef98a506f916
skill-testing is a cursor rule published in the GitHub repository granoflow/granoflow-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 383 tokens to every session, about $0.0019 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
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.