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/issues-angular)<a href="https://agentmods.dev/rules/vepo/issues/issues-angular"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-angular/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/issues-angular"><img src="https://agentmods.dev/badge/rules/vepo/issues/issues-angular.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.00000 | $0.00496 |
| Opus 5.5 | $0.00000 | $0.00198 |
| Sonnet 5.5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
issues-angular 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.
What it actually says
Angular conventions
UI/UX gate
Before any template, style, or interaction change:
- Read docs/ui-elements-gallery.md — reuse documented elements; extend the gallery when adding new ones.
- Apply issues-ux.mdc — Nielsen heuristics checklist and flat UI design language.
Structure
- Components:
src/app/components/<feature>/—*.component.ts,*.html,*.scss. - Services:
src/app/services/*.service.ts—providedIn: 'root'. - Resolvers:
src/app/resolvers/*.resolver.ts. - Routes:
src/app/app.routes.ts.
HTTP
- API types and clients: OpenAPI codegen →
src/app/generated/(gitignored). Regenerate withnpm run generate:apiaftermvn test. - Facades in
services/*.service.tswrap generated*Apiclasses — components inject facades, not generated services directly. - OpenAPI paths already include
/api; setBASE_PATHto''inapp.config.ts(do not double the prefix). - After backend endpoint changes:
mvn test→npm run generate:api→ align facades with generated method signatures (parameter order may differ from path order). - Before marking done:
npm run build(not bareng build—prebuildregenerates the client). - Attach JWT via
auth.interceptor.ts. - SSE stays hand-written in
sse.client.ts.
UI library
- Angular Material for form controls, dialogs, navigation.
- Chart.js via ng2-charts for dashboard widgets.
Tests
*.spec.tsalongside source; Karma/Jasmine.- Mock HTTP with
HttpClientTestingModulein service tests. - Test component behaviour, not implementation details.
Naming
- Selectors:
app-<kebab-case>prefix. - Component class:
XxxComponent; service:XxxService.
Domain language
- UI labels should match docs/domain-specification.md — Ticket, Project, Kanban, not generic "Item" or "Record".
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 · 52 lines · 0 tokens per session scan A 30b5cf83a746
issues-angular is a cursor rule published in the GitHub repository vepo/issues (8 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 496 tokens. 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
external-scale
Source: docs/agents/external-scale.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
ar
Source: docs/agents/ar.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
testing-visual
Source: docs/agents/testing-visual.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
integration-systems
Source: docs/agents/integration-systems.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
development-cycle
Source: docs/agents/development-cycle.md Regenerate: npm run agents:sync -w packages/openbridge-webcomponents -->.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.