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 skills add kok-o/koko-contextos-agents --skill 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/skills/kok-o/koko-contextos-agents/gstack-roles)<a href="https://agentmods.dev/skills/kok-o/koko-contextos-agents/gstack-roles"><img src="https://agentmods.dev/badge/skills/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.1 | $0.00036 | $0.01432 |
| Opus 5 | $0.00018 | $0.00716 |
| Sonnet 5 | $0.00007 | $0.00286 |
| Haiku 4.5 | $0.00004 | $0.00143 |
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 8d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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 ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 153 lines · 36 tokens per session scan A 6cd9a86c137a
gstack-roles is a skill published in the GitHub repository kok-o/koko-contextos-agents (2 stars, last pushed 4d ago), licensed MIT. It adds 36 tokens to every session and 1,432 once invoked, about $0.0002 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 skills, from other repositories
karpathy-coding-principles
Use when andrej Karpathy's 4 coding principles — think before coding, simplicity first, surgical changes, goal-driven execution. Use when coding, reviewing code quality, reducing overengineering,.
universal-patterns
Use when implementing language-agnostic patterns like layered architecture, dependency injection, error handling, or code organization principles across any technology stack.
rust-best-practices
Comprehensive Rust best practices covering ownership, error handling, async patterns, testing, and project structure.
cache_patterns
Instruction set for enabling and operating the Spring Cache abstraction in Spring Boot when implementing application-level caching for performance-sensitive workloads.
event_driven
Structure systems around asynchronous, event-based communication to decouple producers and consumers for improved scalability and resilience. Use when building loosely coupled systems with asynchronous message-based communication.
clean-code
Pragmatic coding standards - concise, direct, no over-engineering, no unnecessary comments.