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/mertcapkin/graphstack/graphstackgit clone --depth 1 https://github.com/MertCapkin/GraphStackWhat 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.01573 | $0.01573 |
| Opus 5 | $0.00787 | $0.00787 |
| Sonnet 5 | $0.00315 | $0.00315 |
| Haiku 4.5 | $0.00157 | $0.00157 |
Grade A, and why
graphstack 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GraphStack Core Rules (v4.7.1)
🎯 Default Mode: Orchestrated
Unless the user explicitly activates a single role, always run as the Orchestrator.
Frictionless startup (Cursor): This project's .cursor/rules/graphstack.mdc is
alwaysApply: true, so Composer/Agent already ships with GraphStack rules in every
new chat. The user does not need to paste Read orchestrator/ORCHESTRATOR.md …
every time.
Your obligation is identical to executing
orchestrator/ORCHESTRATOR.md → Activation on your first substantive turn,
before acting on substantive work.
Optional shortcut: The /graphstack Cursor command (project slash menu) expands
explicit Orchestrator-bootstrap instructions.
These rules are ALWAYS active in this project. Follow them in every response.
🚀 Activation (mandatory first turn — full checklist)
Run one parallel read batch (never split across turns):
orchestrator/TOKEN_OPTIMIZER.md
graphify-out/GRAPH_REPORT.md (if exists)
handoff/BRIEF.md
handoff/board/doing/*.json (note task ids if any)
handoff/STATE.md (last ## block only)
Then greet per orchestrator/ORCHESTRATOR.md step 8.
⛔ First-turn contract (when user message includes a task goal)
The user giving a goal in the same message does NOT mean “implement now”. It means: start the GraphStack cycle — Architect phase only.
ALLOWED turn 1: parallel Activation reads, graph query, cycle start, handoff/BRIEF.md
FORBIDDEN turn 1: any Write/Edit on code paths, implementation, “quick fix” patches
Required sequence before any code file changes:
- Announce
[ARCHITECT MODE] python -m graphstack cycle start <task-id> "<title>"- Write
handoff/BRIEF.md(Status: Ready for Builder) - Orchestrator →
cycle enter-builder→ then[BUILDER MODE]
Never interpret “proceed”, “devam”, or “goal embedded” as permission to code.
If doing/ has a task: read STATE.json role + BRIEF status → offer the matching
cycle enter-* resume (see ORCHESTRATOR step 9c matrix) before code edits.
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 First seen · 168 lines · 1,573 tokens per session scan A c41f018a88c1
graphstack is a cursor rule published in the GitHub repository MertCapkin/GraphStack (8 stars, last pushed 2mo ago), licensed MIT. It adds 1,573 tokens to every session, about $0.0079 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
code-optimization
Guidelines for optimizing duplicate and poorly structured code.
new_features
Guidelines for integrating new features into the Task Master CLI.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.
tasks
Guidelines for implementing task management operations.