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 ai-sdlc-framework/ai-sdlc --skill decision-rubricgit clone --depth 1 https://github.com/ai-sdlc-framework/ai-sdlcWrote 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/ai-sdlc-framework/ai-sdlc/decision-rubric)<a href="https://agentmods.dev/skills/ai-sdlc-framework/ai-sdlc/decision-rubric"><img src="https://agentmods.dev/badge/skills/ai-sdlc-framework/ai-sdlc/decision-rubric/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/ai-sdlc-framework/ai-sdlc/decision-rubric"><img src="https://agentmods.dev/badge/skills/ai-sdlc-framework/ai-sdlc/decision-rubric.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.00168 | $0.03266 |
| Opus 5.5 | $0.00067 | $0.01306 |
| Sonnet 5.5 | $0.00034 | $0.00653 |
| Haiku 4.5 | $0.00017 | $0.00327 |
Grade A, and why
decision-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 19d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decision rubric — how to ask the operator a non-trivial design question
Shallow question-asking is worse than not asking at all. The failure mode this rubric exists to prevent, as the operator who prompted it put it:
"I don't like this new method of resolving the questions. It doesn't go through the thinking rubric we have been doing with the questions that produces meaningful answers — it just skims over the questions and recommends the authors recommendations."
That failure shape: read the OQ → restate the author's lean → ask "agree?". The operator picks "yes" because there's nothing else to compare against, and the decision they thought they were making was actually the author's decision rubber-stamped. Six months later a real edge case surfaces and the resolution is too thin to interpret.
This skill exists so future-you doesn't do that.
When to invoke this rubric
YES — apply the rubric when the user is choosing:
- An open-question or design-decision resolution on any work item — an RFC Open Question, a backlog task's unresolved design point, a GitHub / Jira / Linear issue asking "how should we…", a design-doc comment thread
- A default value that ships to adopters (timeouts, retry counts, grace periods, batch sizes, severity thresholds)
- A library, framework, or major dependency
- An architectural pattern (single-tenant vs multi-tenant, push vs pull, sync vs async, monolith vs split)
- A deprecation / migration / lifecycle policy
- A schema shape that's hard to change later (DB columns, public API contracts, file formats, URI structures)
- A trade-off between two real engineering concerns (performance vs simplicity, strict vs lazy, eager vs lazy)
- Anything where the user's likely answer depends on context they have and you don't
NO — skip the rubric when:
- The choice is a personal preference (file naming, commit message style, which color emoji)
- The choice is fully reversible in <5 minutes (which directory, what to call a variable)
- One option is dominant on every axis (there's no real trade-off)
- The user has already stated a preference in this session or in memory
- You're asking for missing facts ("what's the issue number?", "which branch?") — those get a plain AskUserQuestion or just-ask-in-text
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.
- 19d ago Changed · +13 lines 38b4d6b68778
- 1mo ago First seen · 162 lines · 168 tokens per session scan A 765ed8919453
decision-rubric is a skill published in the GitHub repository ai-sdlc-framework/ai-sdlc (421 stars, last pushed today), licensed Apache-2.0. It adds 168 tokens to every session and 3,266 once invoked, about $0.0007 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 skills, from other repositories
martinloop-govern
Govern coding-agent implementation with MartinLoop budgets, preflight checks, stop conditions, recovery, and verifier-backed evidence.
deploy-registry-server-with-cnpg
Deploy the ToolHive Registry Server to a Kind cluster with CloudNativePG (CNPG) PostgreSQL database. Use when you need a production-like PostgreSQL setup with the CNPG operator.
deploy-registry-server-with-otel
Deploy the ToolHive Registry Server to a Kind cluster with telemetry enabled. Use when you need to deploy the registry server for testing with OTEL metrics and tracing.
air-blackbox-sales-agent
AIR Blackbox's autonomous sales prospecting agent. Finds Python AI projects on GitHub that need EU AI Act compliance, identifies the right person to contact (CEO, CTO, lead maintainer), runs a free compliance scan, and drafts personalized outreach emails that convert to engagement. The sales flow: free scan as the…
interpret-results
Interprets AIR Blackbox scan results and maps findings to specific EU AI Act articles, recitals, and remediation steps. Use when the user has scan output and wants to understand what to fix, why it matters, or how to prioritize.
compliance-scan
Scans a Python AI project for EU AI Act compliance gaps using AIR Blackbox. Use when the user asks to check compliance, scan their code, audit their AI project, or mentions EU AI Act, Articles 9-15, or compliance checking.