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/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/00-project-rules)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/00-project-rules"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/00-project-rules.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.1 | $0.04614 | $0.04614 |
| Opus 5 | $0.02307 | $0.02307 |
| Sonnet 5 | $0.00923 | $0.00923 |
| Haiku 4.5 | $0.00461 | $0.00461 |
Grade A, and why
00-project-rules 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 — 425 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ContextOS — Project Operating System Rules
ContextOS — AI Project Operating System
You are working inside a project managed by ContextOS. This file is the single source of truth for how you must behave, think, and which skills to activate for every task.
Core law: Do not read everything. Read only what the current task requires.
Step 0 — Identify Before Acting
Before writing a single line of code or plan, stop and answer three questions:
1. WHAT DOMAIN? → Frontend / Backend / Architecture / Full-Stack / DevOps
2. WHAT PHASE? → Define / Plan / Build / Verify / Review / Ship
3. WHAT ROLE? → Declare your gstack role for this phase
State your answers explicitly:
[DOMAIN: Frontend] [PHASE: Build] [ROLE: Senior Developer]
Skills loaded: react, typescript, ui-ux-pro, ponytail-mindset
Skill Architecture (Context Efficiency)
Skills are loaded on-demand. To keep the agent context window efficient:
- Keep
SKILL.mdunder 500 lines: Put detailed reference material in separate files. - Use progressive disclosure: Use a
references/directory for deep context and load those files only when specifically needed by the task. - Use
scripts/: Place executable scripts in ascripts/directory alongside the skill.
Skill Registry
All skills live in .agents/core/skills/. Here is what each does and when to use it:
Core Skills (Always Considered)
| Skill | File | Activate When |
|---|---|---|
| engineering-workflow | engineering-workflow/SKILL.md |
Every task — defines the DEFINE→PLAN→BUILD→VERIFY→REVIEW→SHIP pipeline |
| gstack-roles | gstack-roles/SKILL.md |
Every task — declare your specialist role before each phase |
| ponytail-mindset | ponytail-mindset/SKILL.md |
Every BUILD phase — run the 7-rung ladder before writing any code |
| interview-me | interview-me/SKILL.md |
Before /spec — when requirements are ambiguous or need interactive clarification |
| subagent-orchestrator | subagent-orchestrator/SKILL.md |
Parallel tasks — decompose and delegate work across isolated subagents |
| gemini-precision | gemini-precision/SKILL.md |
All Gemini tasks — zero assumptions, zero placeholders, surgical blast radius, test proof |
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 Changed · +66 lines · +1,007 tokens per session c6e7459aa2f9
- 6d ago First seen · 359 lines · 3,607 tokens per session scan A 4247711df867
00-project-rules is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 2d ago), licensed MIT. It adds 4,614 tokens to every session, about $0.0231 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.
grill-me
Interactive assumption-surfacing Q&A that stress-tests a plan through relentless questioning until every decision is resolved. Use when user wants to challenge a plan, validate decisions from conversation/context, or mentions "grill me". For doc-grounded variant, use grill-with-docs.
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.
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…
edit-document
Edit and improve documents by restructuring sections, improving clarity, and tightening prose. Use when user wants to edit, revise, restructure, or improve any document — including specs/ files, articles, READMEs, or technical writing.