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/kok-o/koko-contextos-agents/decisionsgit clone --depth 1 https://github.com/kok-o/koko-contextos-agentsWrote 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/kok-o/koko-contextos-agents/decisions)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/decisions"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/decisions.svg" alt="Measured on agentmods" 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 | $0.00005 | $0.00505 |
| Opus 5 | $0.00003 | $0.00253 |
| Sonnet 5 | $0.00001 | $0.00101 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
decisions 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 3d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: decisions
decision-engine
Overview
A brief summary of what the skill does and its core philosophy.
When to Use
Context for when this skill is applicable.
Rules & Patterns
You manage Architecture Decision Records (ADRs).
Why Decisions Matter
Without ADRs, the AI agent sees:
- "Database: PostgreSQL" — but doesn't know WHY
- "Auth: JWT" — but doesn't know what alternatives were considered
- "Framework: Next.js" — but doesn't know the tradeoffs
With ADRs, the agent understands the reasoning and won't accidentally contradict prior decisions.
Commands
Create a Decision
When an architectural choice is made during any pipeline stage:
- Auto-increment the decision number
- Use the template from
generators/templates/DECISION.md - Save to
docs/decisions/NNNN-decision-name.md - Update the Project Graph if the decision affects modules
Naming convention: docs/decisions/0001-use-postgresql.md
Query Decisions
Before making changes that touch architecture:
- Check
docs/decisions/for related decisions - If a decision exists, follow it
- If a decision needs to change, create a new ADR that supersedes the old one
Decision Lifecycle
proposed → accepted → [deprecated | superseded]
- proposed: Under discussion, not yet committed
- accepted: The team agreed, this is the standard
- deprecated: No longer relevant (project evolved)
- superseded: Replaced by a newer decision (link to it)
Auto-Detection
The Decision Engine should suggest creating an ADR when it detects:
- A new database/ORM is introduced
- A new framework is added
- Authentication strategy changes
- API versioning approach is chosen
- Deployment strategy is decided
- A significant library is added (state management, testing framework, etc.)
Code Examples
See EXAMPLES.md for detailed code examples.
Validation Checklist
What to verify during the review phase before completing the task.
Common Mistakes
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.
- 3d ago First seen · 93 lines · 5 tokens per session scan A c110728fa8c6
decisions is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 3d ago), licensed MIT. It adds 5 tokens to every session and 505 once invoked, about $0.0000 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
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…
react-rerender-optimization
React re-render optimization patterns including memo, useMemo, useCallback, useState, useRef, and derived state. Use when components re-render too often, dealing with stale closures, dependency arrays, performance issues, or optimizing slow components.
index
This project uses Unity 6.2 (LTS 2025) with modern systems and architectural approaches.
general-typescript-rule
Applies general TypeScript best practices and style guidelines to all TypeScript files in the project.
readme-best-practices
README Best Practices - enforces high-quality README patterns when creating or editing README files.
pull-request-changelist-instructions
Guidelines for creating consistent pull request changelists in markdown format with proper code block formatting.