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/consensys/ask-o11y-plugin/quality-workflowgit clone --depth 1 https://github.com/Consensys/ask-o11y-pluginWhat 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.00423 | $0.00423 |
| Opus 5 | $0.00211 | $0.00211 |
| Sonnet 5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00042 | $0.00042 |
Grade A, and why
quality-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 2d 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
Quality Workflow
Reference: CLAUDE.md is the authoritative source.
Quality Gates (after every code change)
Run these steps after every code change:
- Build compiles —
npm run build(frontend) +npm run build:backend(Go) - OpenAPI spec — update
pkg/plugin/openapi/openapi.jsonand runvalidate:openapiif routes changed - Code review — fix critical/major/medium issues
- Clean AI noise — remove comments that restate code; only keep non-obvious why comments
- Tests & lint —
npm run test:ci,go test ./pkg/...,npm run lint,npm run typecheck
Commands
# Always prefix npm commands with nvm use 22 &&
nvm use 22 && npm run test:ci # Frontend unit tests
go test ./pkg/... # Backend tests
nvm use 22 && npm run lint # ESLint
nvm use 22 && npm run typecheck # TypeScript
nvm use 22 && npm run validate:openapi # OpenAPI validation
Severity Policy
| Severity | Action |
|---|---|
| Critical | Fix now |
| Major | Fix before commit |
| Medium | Fix before PR |
| Low | Optional |
Commit Format (CI-enforced)
Format: type(scope): description — lowercase, imperative, no period.
Types: feat, fix, docs, style, refactor, perf, test, build, ci, chore, revert
Scopes: chat, mcp, session, config, rbac, oauth, share, viz, backend, ui, frontend, deps, release, ci, main
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.
- 2d ago First seen · 47 lines · 423 tokens per session scan A 40a66fc193ff
quality-workflow is a cursor rule published in the GitHub repository Consensys/ask-o11y-plugin (40 stars, last pushed 7d ago), licensed MIT. It adds 423 tokens to every session, about $0.0021 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 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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.