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 qualityclouds/norma-mcp --skill norma-workflowgit clone --depth 1 https://github.com/qualityclouds/norma-mcpWrote 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/qualityclouds/norma-mcp/norma-workflow)<a href="https://agentmods.dev/skills/qualityclouds/norma-mcp/norma-workflow"><img src="https://agentmods.dev/badge/skills/qualityclouds/norma-mcp/norma-workflow/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/qualityclouds/norma-mcp/norma-workflow"><img src="https://agentmods.dev/badge/skills/qualityclouds/norma-mcp/norma-workflow.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.00061 | $0.00597 |
| Opus 5.5 | $0.00024 | $0.00239 |
| Sonnet 5.5 | $0.00012 | $0.00119 |
| Haiku 4.5 | $0.00006 | $0.00060 |
Grade A, and why
norma-workflow 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Norma workflow
Norma gives you the rules for the detected stack before you write, checks each file against them, and records the outcome. The same file and the same rules return the same verdict every time, and every check leaves a record.
When to use
- Any task that creates or modifies code while the Norma MCP server is connected
- Reviewing a file or a change against the organization's coding standards
- Working through the open issues from the repository's last full scan
Writing or modifying code
Before the first check, the repository must be linked in the user's Norma
account (GitHub or Bitbucket integration at norma.qualityclouds.com).
live_check, get_open_issues and register_applied_actions only run on a
linked repository. Pass the repository's public remote URL with each call.
get_rulesets: at the start of the task. Norma detects the stack with no configuration and returns the applicable rulesets.get_rules_for_ruleset: for each relevant ruleset ID. Never skip this step. The rules must be in context before you write.- Write or modify the code with those rules in context.
live_check: after each file is created or modified, before moving on. Fix what it returns and re-check until the file passes.register_applied_actions: after the task, using the exact rule IDs from step 2. Record rules verified compliant, violations fixed (file and lines), violations prevented during generation, and which model did the work.
Working through standing issues
Call get_open_issues for the open issues from the last full scan, each with
the context needed to fix it. Fix them, verify each fix with live_check, and
record the outcome with register_applied_actions.
Rules of the loop
- Never claim a file passes without a
live_checkresult that says so. - Never invent or paraphrase rule IDs. Use the IDs returned by
get_rules_for_ruleset. - If a call reports the repository isn't linked, stop and tell the user to
link it in their Norma account. Do not report code as checked until a
live_checkon the linked repository says so. The user's code is never stored in their Norma account. - Findings and the repository's Production-Ready Score live in the user's workspace at norma.qualityclouds.com. Point the user there for full results.
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 · +5 lines 3ac649f516f8
- 1mo ago First seen · 52 lines · 61 tokens per session scan A 06c172facc1f
norma-workflow is a skill published in the GitHub repository qualityclouds/norma-mcp (5 stars, last pushed 19d ago), licensed MIT. It adds 61 tokens to every session and 597 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
incident-response
Incident management lifecycle — triage, communicate, mitigate, postmortem. Three modes — new (start incident), update (status update), postmortem (blameless RCA report).
logic-review
Find logic bugs in a single file or function via semi-formal execution tracing (Premises → Trace → Divergence → Trigger → Remedy). Trigger when a user shares code and suspects something is wrong without naming a concrete failure — phrases like "review this", "does this look right", "check this function", "audit this…
logic-fix-all
Autonomous repository-wide audit-and-fix pipeline: health → review → locate/explain → fix → diff-verify → iterate until clean. Starts with a mandatory consent prompt (token-intensive); after consent runs hands-free. Trigger when the user wants ALL logic issues found and fixed — "fix everything", "fix all logic…
logic-health
Sweep a directory, module, or full codebase for logic correctness and produce a scored health dashboard with systemic patterns. Trigger when the user requests a health view — "audit the whole codebase", "health check", "health overview", "logic health overview", "audit src/", "audit auth and payments modules", "where…
discover
Primary router for discovery, debugging, investigation, quality, and exploration workflows. Analyzes user intent and dispatches to debug, bughunt, quick-review, deep-review, coverage, testing-strategy, learn, tour, impact, assist-review. The recommended entry point for any 'find out', 'check', 'review', or…
logic-locate
Locate the root cause of a CONFIRMED failure via backward-then-forward semi-formal tracing. Trigger when the user provides a stack trace, failing assertion, error message, or specific wrong-value observation — "find the bug", "this test is failing", "track down this crash", "why is this test failing", "KeyError at…