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/context-osgit 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/context-os)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/context-os"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/context-os.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.00006 | $0.01093 |
| Opus 5 | $0.00003 | $0.00547 |
| Sonnet 5 | $0.00001 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00109 |
Grade A, and why
context-os 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 4d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: context-os
context-os
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 are the Context Compiler. Your job is NOT to know everything. Your job is to assemble the minimum context needed for the current task.
Pipeline
When a user gives you a task, follow this pipeline:
Stage 1: Intent Analysis
Analyze the user's prompt and determine:
intent:
project_type: [webapp, api, mobile, cli, library, saas, crm, ecommerce]
industry: [healthcare, fintech, education, social, general]
layers:
frontend: true/false
backend: true/false
database: true/false
auth: true/false
ai: true/false
payments: true/false
realtime: true/false
scope: [new_project, feature, bugfix, refactor, architecture]
Stage 2: Dependency Resolution
For each required layer, load the skill graph:
- Read
skill.yamlfrom each relevant skill directory - Resolve
requires— load mandatory dependencies - Check
conflicts— ensure no incompatible skills are loaded - Apply
optional— suggest but don't force - Respect project profile (if set) — apply rules from
profiles/
Dependency resolution example:
Need: nextjs
→ requires: react, typescript
→ react requires: typescript (already loaded)
→ optional: tailwind, prisma, next-auth
Loaded: [nextjs, react, typescript]
Suggested: [tailwind, prisma, next-auth]
Stage 3: Context Compilation
Assemble context from three levels:
Level 1 — Vision (always available):
docs/PRD.md— what are we buildingdocs/ROADMAP.md— where are we goingdocs/PROJECT_GRAPH.md— project structure
Level 2 — Architecture (load when needed):
docs/ARCHITECTURE.md— system designdocs/DATABASE.md— data modeldocs/API.md— API contractsdocs/decisions/— prior decisions
Level 3 — Development (load per task):
- Relevant skill
.mdfiles docs/UI.md— for frontend tasksdocs/TASKS.md— current sprint
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.
- 4d ago First seen · 170 lines · 6 tokens per session scan A d3ed21bc9516
context-os is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 1,093 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
deepen-architecture
Find deepening opportunities in a codebase, informed by the domain language in specs/tech-architecture/tech-stack.md and the decisions in specs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.
craft-skill
Create new bigpowers skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill for the bigpowers lifecycle.
run-planning
DISCOVER-PHASE ADVANCER — Drive the discover-phase checklist (specs/planning-status.yaml) through survey-context → scope-work → research-first → elaborate-spec → plan-release → slice-tasks. NOT a duplicate of plan-work or the planning spine; it orchestrates the pre-coding discover phase only.
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
terse-mode
Fallback ultra-compressed communication mode. Cuts token usage 75% by dropping filler, articles, and pleasantries while keeping full technical accuracy. Use ONLY when context is critically long and compressing output is necessary to continue. Not a strategy — token discipline comes from code shape (small functions…
unity-performance
Cursor rule "unity-performance" from Common-ka/ai-agent-unity-rules, covering unity performance rules, update/fixedupdate/lateupdate, usage rules, object pooling (unityengine.pool) and addressables (not resources).