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 Qualimetry/claude-code-qualimetry-ai-app --skill blitzy-rulesgit clone --depth 1 https://github.com/Qualimetry/claude-code-qualimetry-ai-appWrote 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/qualimetry/claude-code-qualimetry-ai-app/blitzy-rules)<a href="https://agentmods.dev/skills/qualimetry/claude-code-qualimetry-ai-app/blitzy-rules"><img src="https://agentmods.dev/badge/skills/qualimetry/claude-code-qualimetry-ai-app/blitzy-rules/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/qualimetry/claude-code-qualimetry-ai-app/blitzy-rules"><img src="https://agentmods.dev/badge/skills/qualimetry/claude-code-qualimetry-ai-app/blitzy-rules.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.00096 | $0.00758 |
| Opus 5 | $0.00048 | $0.00379 |
| Sonnet 5 | $0.00019 | $0.00152 |
| Haiku 4.5 | $0.00010 | $0.00076 |
Grade A, and why
blitzy-rules 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 9d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blitzy Rules Packs
When asked to produce Blitzy rules for a project so that Blitzy generates code compliant with the organisation's standards, follow this workflow.
Step 1: Choose the Pack
- Coding standards pack (both Qualimetry AI and Enterprise): policies, coding principles, and language coding standards. Use
get_coding_standards_blitzy. - Analysis rules pack (Qualimetry Enterprise only): the rules-based analysis rule set for a language. Use
get_rules_based_analysis_rules_blitzy.
Step 2: Fetch the Pack
Coding standards: Call get_coding_standards_blitzy. Returns policies and principles by default; pass languageCodes to add language coding standards. Narrow with:
includePolicies(default true)includePrinciples(default true)languageCodes- comma-separated codes (e.g.csharp,java,python) for the project's language(s). Required to receive language coding standards; if omitted, only policies and principles are returned. Pass the project's primary language(s) so the pack carries the relevant language rules.collapseLanguageFolders(default true) - one folder per language with{category}--{subcategory}.rule.mdfilenames; set false to nest categories as folders
Analysis rules: Call get_rules_based_analysis_rules_blitzy with:
languageCode(required, e.g.csharp)qualityProfileName(optional; blank returns every rule for the language)collapseLanguageFolders(default true) - one folder per language with{type}--{attribute}.rule.mdfilenames
Step 3: Write the Pack
Both tools return one JSON object:
license- the proprietary licence notice (coding-standards pack only). Preserve it; it is also written asLICENSE.mdinfiles.rules- the structured rules for API-based publishing to a Blitzy endpoint.files- an array of{ path, content }pairs that mirror the zip tree. Write each file verbatim to disk (or to the target repository) at itspath, preserving the directory structure.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 56 lines · 96 tokens per session scan A a4e35e8e4e91
blitzy-rules is a skill published in the GitHub repository Qualimetry/claude-code-qualimetry-ai-app (1 stars, last pushed 5d ago), licensed Apache-2.0. It adds 96 tokens to every session and 758 once invoked, about $0.0005 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 skills, from other repositories
improve-code-quality
Guided journey from a working-but-untested vibe-coded prototype to a production-ready product with tests, clean structure, a business-rules boundary, and resilience at scale. Orchestrates nine skills phase by phase - working-with-legacy-code, clean-code, refactoring-patterns, software-design-philosophy…
refactoring-patterns
Apply named refactoring transformations to improve code structure without changing behavior. Use when the user mentions "refactor this", "code smells", "extract method", "replace conditional", "technical debt", "move method", "inline variable", "decompose conditional", or "clean up this messy code". Also trigger when…
team-review
Review changed code for reuse, quality, and efficiency using a team of persistent named reviewers. This skill should be used when the user says "team review", "review with team", or wants parallel code review with persistent team members for follow-up questions. Similar to /subagent-review but reviewers persist after…
roslyn-query
Query .NET/C# codebases using Roslyn AST analysis via dotnet run file. Use for tracing data flow, auditing API usage, finding pattern violations, or ad-hoc codebase queries.
review-responder
Use when receiving feedback on code you implemented, responding to reviewer comments, deciding which review suggestions to implement, or pushing back on incorrect review feedback.
codex
Route a task to OpenAI's Codex CLI (codex exec) instead of doing it yourself. Use this skill ANY time the user names codex or types /codex — even for routine work Claude could handle, because the user is choosing to delegate. The intent: 'ask codex', 'have codex review/refactor this', 'check/validate with codex', 'see…