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.
git clone --depth 1 https://github.com/vepo/issuesWrote 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/rules/vepo/issues/static-analysis)<a href="https://agentmods.dev/rules/vepo/issues/static-analysis"><img src="https://agentmods.dev/badge/rules/vepo/issues/static-analysis/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/rules/vepo/issues/static-analysis"><img src="https://agentmods.dev/badge/rules/vepo/issues/static-analysis.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.00527 | $0.00527 |
| Opus 5.5 | $0.00211 | $0.00211 |
| Sonnet 5.5 | $0.00105 | $0.00105 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
static-analysis 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 1mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Static analysis — finish checklist
Working code only: do not end development — done or in-progress — with a failing mvn verify, broken npm run build, or compile/linter errors in files you changed. Fix or revert first.
Before marking a coding task done, run local checks only (no SonarCloud tokens required for the gate).
When to run
- After production or test code changes (Java, SQL migrations, TypeScript you edited).
- Skip for docs-only,
.mdcrules-only, or comment-only edits.
Required commands
Primary gate — align with .github/workflows/build.yml:
mvn verify
When Angular files changed, also run:
cd src/main/webui && npm run build
cd src/main/webui && npm test -- --no-watch --browsers=ChromeHeadless
npm run build runs generate:api (via prebuild) then ng build — required before marking done; do not rely on ng build alone after API changes.
Formatting (optional, faster feedback):
mvn formatter:format
IDE diagnostics
On changed source files, run ReadLints and fix new errors and warnings in paths you touched.
What to fix
- Compile errors and test failures from
verify. - Formatting violations —
formatter.xmlvia issues-format-imports.mdc. - New linter warnings in edited files.
- Obvious smells you introduced — align with issues-java.mdc and issues-core.mdc.
Pre-existing issues in unrelated files: fix only if trivial; do not scope-creep.
Do not finish while
mvn verifyfails on your branch.npm run buildfails whensrc/main/webui/**was changed.- Linter reports new problems in files you changed.
- You knowingly left failing tests in touched code.
- You would leave the workspace in a non-runnable state — revert partial work or complete the fix loop first.
Report to the user
When wrapping up, briefly note: verify (pass / fail fixed), formatter (ok / applied), linter (clean / issues fixed).
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.
- 1mo ago First seen · 64 lines · 527 tokens per session scan A 465ef1b1f136
static-analysis is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 527 tokens to every session, about $0.0021 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-31.
Other cursor rules, from other repositories
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
pages
Source: docs/agents/pages.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
css-render-blocking-diagnosis
Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
5-bug-finder
APPLY WHEN investigating a bug.
optimisation-rules
Performance optimization with evidence-based improvements.