data

A placeholder for project-specific guidance about data and database decisions. It currently contains no actual project rules or facts.

In plain words
What is it for?
Use it as a place to record data models, storage choices, data workflows, and other project-specific details once they are known.
Why use it?
It signals that the agent should ask before making lasting data-related decisions, instead of guessing from incomplete information.

Agent

Install

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.

agentmods
npx agentmods add agents/hannsxpeter/scriveno/data
Clone the repo
git clone --depth 1 https://github.com/hannsxpeter/scriveno
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 139 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00139
Opus 5 $0.00000 $0.00069
Sonnet 5 $0.00000 $0.00028
Haiku 4.5 $0.00000 $0.00014

Measured 2d ago against content hash 9d3258a59c58, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

data 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • data — 100% identical, 0 lines differ
agents/data.md · 42 lines

What it actually says

Scope

(stub) Capture project-specific guidance for data.

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 data decisions.
Changes

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.

  1. 2d ago First seen · 42 lines · 0 tokens per session scan A 9d3258a59c58

Subscribe to this mod's changes

data 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 139 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.

Related

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.

myICOR/myPKA · 64 tokens

story-explorer

故事项目结构化查询 agent(只读)。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息, 返回结构化 JSON 摘要。 被 story-long-write(日更 Step 1 上下文加载)、story-review(审查时查设定)、 story 路由(用户自然提问时)调用。 不做任何创作判断或修改。.

zenstory-ai/oh-story-claudecode · 104 tokens

story-architect

故事架构与世界观创作专家。负责题材选择、核心梗设计、世界观构建、大纲排布、 钩子/悬念/反转等叙事工程、情绪弧线设计、范围控制审查。 被 story-long-write(Phase 1-3)、story-short-write(Phase 1-2)调用。 也可审查已有内容的结构问题。.

zenstory-ai/oh-story-claudecode · 90 tokens

story-explorer

故事项目结构化查询 agent(只读)。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息, 返回结构化 JSON 摘要。 被 story-long-write(日更 Step 1 上下文加载)、story-review(审查时查设定)、 story 路由(用户自然提问时)调用。 不做任何创作判断或修改。.

Xiaoyangy/novel-studio · 104 tokens

consistency-checker

事实一致性与伏笔状态检查专家(只读)。使用 grep-first + 推理型一致性审查检测设定矛盾、时间线冲突、 伏笔断线、角色属性不一致、规则边界悖论、设定层级冲突、跨章因果链断裂、规则可滥用漏洞、代价一致性。输出 S1-S4 分级冲突报告。 被 story-review、story-long-write(Phase 5)、story-short-write(Phase 4)调用。 不做任何创作判断。.

Xiaoyangy/novel-studio · 120 tokens

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.

german-krasnikov/unity-biome-mcp · 53 tokens