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 granoflow/granoflow-mcp-server --skill granoflow-project-sotgit clone --depth 1 https://github.com/granoflow/granoflow-mcp-serverWrote 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/granoflow/granoflow-mcp-server/granoflow-project-sot)<a href="https://agentmods.dev/skills/granoflow/granoflow-mcp-server/granoflow-project-sot"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-project-sot/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/granoflow/granoflow-mcp-server/granoflow-project-sot"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-project-sot.svg" alt="Reviewed on agentmods" width="80" 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.00077 | $0.00967 |
| Opus 5 | $0.00039 | $0.00483 |
| Sonnet 5 | $0.00015 | $0.00193 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
granoflow-project-sot 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 10d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Granoflow Project SoT
Single owner for the mutable project orchestration SoT in the target repo:
temp/project-sot.yaml
It records lifecycle stages, coarse work_items, next_step, thin campaign
gates, and evidence pointers only. Skill-internal Grill / suite-merge
details stay out of this file.
Keyword
#project-sot#重生SoT#regen-project-sot
When to use
- Starting or resuming a long / unattended project run.
- Host-wake ticks that must load Layer A continuity.
temp/wiped ortemp/project-sot.yamlmissing → regen before continue.- User asks to refresh SoT to match App / workspace verify status.
- Closing IT/E2E / final delivery when updating campaign thin gates on the SoT.
Not this Skill
| Concern | Owner |
|---|---|
| Running Flutter UI E2E | granoflow-e2e-test-campaign |
| Portfolio IT loop | granoflow-integration-test-campaign |
| Project Work intake | granoflow-project-definition |
| Wake protocol details | granoflow-agent-workflow → long-task-run-continuity |
Mandatory loads
granoflow_bundled_skill_reference(
skillId: "granoflow-project-sot",
referenceId: "project-sot"
)
On regen:
granoflow_bundled_skill_reference(
skillId: "granoflow-project-sot",
referenceId: "regen-from-app"
)
Also load long-task-run-continuity when arming or consuming host wake
(Layer A = this SoT).
Hard rules
- One file owns
next_step: onlytemp/project-sot.yaml. - Forbidden as orchestration SoT:
unattended-run-ledger.yaml,residual-report.*,project-lifecycle-progress-board.md,campaign-state.json, coverage-matrix / closing-summary bodies. Those may exist as evidence; they must not pinnext_step. - New writes are YAML only (
doc_type: project_sot,schema: granoflow_project_sot_v1). - Legacy
temp/project-e2e-sot-v*.mdis read-only compatibility; migrate totemp/project-sot.yamlbefore claiming stage progress. - Missing SoT on unattended resume → run regen, then lint, then continue.
Skipping fails closed as
project_sot_missing.
What ships with it
5 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.
- 10d ago First seen · 118 lines · 77 tokens per session scan A f4b69e432bd0
granoflow-project-sot is a skill published in the GitHub repository granoflow/granoflow-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 967 once invoked, about $0.0004 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.