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/joaovicdev/nemesis/architecturegit clone --depth 1 https://github.com/joaovicdev/nemesisWhat 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.00556 | $0.00556 |
| Opus 5 | $0.00278 | $0.00278 |
| Sonnet 5 | $0.00111 | $0.00111 |
| Haiku 4.5 | $0.00056 | $0.00056 |
Grade A, and why
architecture 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 yesterday.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Rules
Layer Separation
NEMESIS is divided into four strict layers. Imports must only flow downward — upper layers depend on lower ones, never the reverse.
tui/ ← presentation only, no business logic
core/ ← domain models, config, project state
agents/ ← orchestrator, analyst, executor (AI + tool logic)
db/ + tools/ ← persistence and external tool wrappers
tui/MUST NOT import fromagents/directly. All agent interaction goes throughcore/.agents/MUST NOT import fromtui/. Agents communicate results via events or callbacks registered bycore/.tools/contains only thin wrappers that execute system commands and return raw output. No analysis or interpretation belongs here.
Agent Patterns
- All agents (
orchestrator,analyst,executor) areasyncclasses. - Agents communicate results by emitting typed
FindingorAgentEventobjects. - Executors are short-lived: instantiated per task, execute, emit result, and are garbage-collected.
- The Orchestrator holds the only long-lived context object (
ProjectContext). - The Analyst ALWAYS processes raw tool output before it reaches the Orchestrator. Raw subprocess output must never be sent directly to the LLM as-is.
Data Flow
User input → Orchestrator → [spawns] Executor(s)
↓ raw output
Analyst
↓ structured Finding
Orchestrator ← Finding
↓
ProjectContext (SQLite)
↓
TUI update
Destructive Action Gate
Any tool or agent action that is potentially destructive (exploit execution, brute force, file upload, lateral movement) MUST:
- Be tagged with
destructive=Truein its tool definition. - Emit a
ConfirmationRequiredevent to the TUI before execution. - Only proceed after receiving an explicit
UserConfirmedevent. - Log the confirmation with timestamp to the project session.
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.
- yesterday First seen · 71 lines · 556 tokens per session scan A 33a7f9dce447
architecture is a cursor rule published in the GitHub repository joaovicdev/nemesis (4 stars, last pushed 4mo ago), licensed MIT. It adds 556 tokens to every session, about $0.0028 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 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.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.