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 skills/dheerg/swarms/define-rubricnpx skills add DheerG/swarms --skill define-rubricgit clone --depth 1 https://github.com/DheerG/swarmsWrote 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/dheerg/swarms/define-rubric)<a href="https://agentmods.dev/skills/dheerg/swarms/define-rubric"><img src="https://agentmods.dev/badge/skills/dheerg/swarms/define-rubric.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.00024 | $0.00196 |
| Opus 5 | $0.00012 | $0.00098 |
| Sonnet 5 | $0.00005 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
define-rubric 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 6d 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
The team can't find existing standards. Help them build a rubric.
Ask: what does the output look like when it's right? Get specific, measurable answers. File sizes, response times, value ranges, visual correctness, behavioral expectations. If the user or team can't quantify it, ask what they'd check manually. If they don't know the values yet, the rubric item becomes an experiment: produce a sample, measure the property, decide if it's acceptable.
The rubric is a short list of pass/fail criteria the team agrees on before execution starts. Keep it concrete.
The team will review output against these criteria in a loop — refining until confidence reaches 9/10+. Write criteria that guide improvement, not just pass/fail. When no test suite exists, this rubric is the testing framework.
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.
- 6d ago First seen · 15 lines · 24 tokens per session scan A bfe9cc9c3aac
define-rubric is a skill published in the GitHub repository DheerG/swarms (85 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 196 once invoked, about $0.0001 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
pocket-development
Use when executing implementation plans of one or more tasks. Trigger on execute plan, delegate tasks, dispatch subagents. Combines delegate handoff discipline with prompt-engineering attention mechanics.
pocket-planning
Converts a pocket-grinding spec into a TDD-structured execution plan of full Pocket Packets. Use when pocket-grinding handoff arrives (spec path + acceptance criteria). Trigger on "create plan", "build plan", "pocket-planning", or when pocket-grinding skill invokes this. Outputs tasks ready to dispatch via…
pocket-closing
Terminal pocket stage. User invokes after pocket-development's phase-level pass writes verdicts. Reconciles reviews against log.json, gates on REVIEWFAIL/REVIEWBLOCKED, advances REVIEW→DONE, runs log close, and emits a closeout summary. Trigger on "pocket-closing", "close the plan", "close out", "finalize plan", or…
pocket-grinding
BDD-driven feature/fix discovery before any implementation. Use when planning a feature, designing a fix, or exploring options before building. Trigger on "pocket-grinding", "brainstorm", "think through", "plan this", "before we build". Invokes pocket-planning at handoff.
pocket-help
Onboarding and routing guide for the Pocket skill ecosystem. Use when someone asks what Pocket is, which Pocket skill to use, how the end-to-end flow works, or when Pocket is better than lighter Superpowers-style flows. Trigger on "what is pocket", "how do I use pocket", "which pocket skill", "explain pocket"…
structured-research
Standalone skill for validating an explicit assumption with structured research. Use when a user holds a belief that is still an assumption — a technical claim, a library's behavior, a "this is probably how X works" — and wants it investigated methodically before it leaks into planning or code. Recommends a research…