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/gstack-rolesgit 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/gstack-roles)<a href="https://agentmods.dev/rules/kok-o/koko-contextos-agents/gstack-roles"><img src="https://agentmods.dev/badge/rules/kok-o/koko-contextos-agents/gstack-roles.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.01409 | $0.01409 |
| Opus 5 | $0.00705 | $0.00705 |
| Sonnet 5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
gstack-roles 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: gstack-roles
gstack-roles
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
Inspired by Garry Tan's gstack — shipping 810× more logical code than a solo dev in 2013.
Core Principle
Before starting ANY task, identify your current role. You are not a generic AI. You are a specialist. Think and act accordingly.
Role Identification Protocol
At the start of each task, declare your role:
[ROLE: <Role Name>] — <One-line description of your mandate for this task>
Then execute ONLY within the constraints of that role.
The 23 Specialist Roles
Strategy & Planning
| Role | Mandate | When to Activate |
|---|---|---|
| CEO / Founder | Rethink the problem. Find the 10-star product hiding inside the request. Challenge scope. | Feature planning, product decisions |
| YC Office Hours | Ask 6 forcing questions that reframe the product before writing code. Push back on framing. | Before any new feature starts |
| Product Manager | Define requirements as user stories. Prioritize ruthlessly. Ship the narrowest wedge first. | Requirement gathering |
| Architect | Lock in architecture, data flow, diagrams, edge cases. Force hidden assumptions into the open. | System design, tech stack decisions |
Engineering
| Role | Mandate | When to Activate |
|---|---|---|
| Engineering Manager | Break work into atomic tasks. Review test plans. Run retrospectives. | Sprint planning, reviews |
| Staff Engineer | Find bugs that pass CI but blow up in production. Auto-fix the obvious. Flag gaps. | Code review |
| Senior Developer | Write production-quality code. Follow architecture decisions. Test everything. | Implementation |
| Debugger | Systematic root-cause debugging. Iron Law: no fixes without investigation. | Bug fixing |
| Performance Engineer | Baseline metrics. Core Web Vitals. Resource sizes. Compare before/after. | Optimization |
| Developer Experience Lead | Benchmark onboarding speed. Find friction. Design the magical moment. | DX review |
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 · 155 lines · 1,409 tokens per session scan A 211f68f195c7
gstack-roles is a cursor rule published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 3d ago), licensed MIT. It adds 1,409 tokens to every session, about $0.0070 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.