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 agents/hannsxpeter/scriveno/stackgit clone --depth 1 https://github.com/hannsxpeter/scrivenoWhat 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.00000 | $0.00428 |
| Opus 5 | $0.00000 | $0.00214 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
stack 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 2d 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.
What it actually says
Scope
(stub) Capture project-specific guidance for stack.
Context
(stub) Fill with facts an agent cannot reliably infer from code alone.
Decisions
(none)
Rules
(none)
Workflows
(none)
Watchouts
(none)
Touchpoints
(none)
Gaps
- This pillar is a stub. Ask before making durable stack decisions.
Godpowers artifact sources
- Sync mode: proposed for review.
- Related artifact:
.godpowers/stack/DECISION.mdx. - Rule: keep this pillar aligned when these artifacts change durable stack truth.
Extracted durable signals
From .godpowers/stack/DECISION.mdx:
- [DECISION] This artifact was generated from imported planning-system context.
- [DECISION] Treat this artifact as a Godpowers seed until a specialist command validates or rewrites it.
- [DECISION] Imported source files remain historical evidence, not Godpowers source of truth.
- [HYPOTHESIS] legacy planning source .planning/archive/01-12-historical-REVIEW-FIX.md may inform this artifact.
- [HYPOTHESIS] Imported signal from .planning/archive/01-12-historical-REVIEW-FIX.md: Historical Phases 1-12: Review Fix Summary.
- [HYPOTHESIS] Imported signal from .planning/archive/01-12-historical-REVIEW-FIX.md: Scope.
- [HYPOTHESIS] Imported signal from .planning/archive/01-12-historical-REVIEW-FIX.md: Fixed Findings.
- [HYPOTHESIS] legacy planning source .planning/archive/HISTORICAL-VALIDATION-NOTES-01-08.md may inform this artifact.
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.
- 2d ago First seen · 62 lines · 0 tokens per session scan A 2e728a15c53f
stack is an agent published in the GitHub repository hannsxpeter/scriveno (9 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 428 tokens. 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 agents, from other repositories
mack
Automation Specialist. Use proactively for API integrations, MCP server setup, webhook receivers, OAuth flows, automations, and the connection layer of external imports (fetch the bytes from a live API or auth-gated source, hand off to Silas). Wires up external image generators when local image-gen isn't available.
story-explorer
故事项目结构化查询 agent（只读）。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息， 返回结构化 JSON 摘要。 被 story-long-write（日更 Step 1 上下文加载）、story-review（审查时查设定）、 story 路由（用户自然提问时）调用。 不做任何创作判断或修改。.
story-architect
故事架构与世界观创作专家。负责题材选择、核心梗设计、世界观构建、大纲排布、 钩子/悬念/反转等叙事工程、情绪弧线设计、范围控制审查。 被 story-long-write（Phase 1-3）、story-short-write（Phase 1-2）调用。 也可审查已有内容的结构问题。.
story-explorer
故事项目结构化查询 agent（只读）。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息， 返回结构化 JSON 摘要。 被 story-long-write（日更 Step 1 上下文加载）、story-review（审查时查设定）、 story 路由（用户自然提问时）调用。 不做任何创作判断或修改。.
consistency-checker
事实一致性与伏笔状态检查专家（只读）。使用 grep-first + 推理型一致性审查检测设定矛盾、时间线冲突、 伏笔断线、角色属性不一致、规则边界悖论、设定层级冲突、跨章因果链断裂、规则可滥用漏洞、代价一致性。输出 S1-S4 分级冲突报告。 被 story-review、story-long-write（Phase 5）、story-short-write（Phase 4）调用。 不做任何创作判断。.
unity-scene-editor
Use to inspect or modify Unity scenes, GameObjects, components, assets, UI, animation, physics, materials, or VFX through Unity Biome MCP. Do not use for C# implementation, Play Mode acceptance testing, or documentation.