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/ysfaskri/archguardian/suppressgit clone --depth 1 https://github.com/ysfAskri/archguardianWhat 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.00000 | $0.00135 |
| Opus 5 | $0.00000 | $0.00068 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
suppress 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
Suppress archguardian findings
When the user wants to suppress a false positive:
- Prefer rule-specific over blanket:
// archguard-ignore-line security/xssover// archguard-ignore-line - Same-line for short lines, next-line for long lines
- Python uses
#, block comments/* */also work - After adding, re-scan to confirm suppression works
- If many false positives of the same type, suggest disabling the rule in
.archguard.ymlinstead
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 · 16 lines · 0 tokens per session scan A f76a8c277225
suppress is a cursor rule published in the GitHub repository ysfAskri/archguardian (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 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
cli-forge-schema
Generate GitHub-compatible Mermaid diagrams — auto-picks diagram type, splits complex ones, converts tables/kanban/PERT.
cursorrules
Cursor rule "cursorrules" from me2resh/agent-decision-record, covering agent decision records (agdr) — cursor rules, purpose, see: https://github.com/me2resh/agent-decision-record, decision detection and adding a new dependency → stop, document decision first.
agdr
Agent Decision Records - enforces structured documentation of technical decisions before implementation.
react-composition-patterns
React composition patterns for scalable component architecture including compound components, context providers, state management, boolean prop alternatives, render props vs children, and React 19 API changes. Use when refactoring components with many boolean props, building component libraries, designing flexible…
cursorrules
Cursor rule "cursorrules" from barrosohub/frontend-stack-blueprint, covering frontend stack blueprint, stack, architecture (mandatory), universal execution protocol (technology-agnostic) and production reliability (mandatory by applicable profile).
005-whitespace
005: Eliminate stray or consecutive blank-line suggestions.