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 skills/o-1717986918/arcvellum/_enginenpx skills add o-1717986918/arcvellum --skill _enginegit clone --depth 1 https://github.com/o-1717986918/arcvellumWrote 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/o-1717986918/arcvellum/_engine)<a href="https://agentmods.dev/skills/o-1717986918/arcvellum/_engine"><img src="https://agentmods.dev/badge/skills/o-1717986918/arcvellum/_engine.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.00000 | $0.00320 |
| Opus 5 | $0.00000 | $0.00160 |
| Sonnet 5 | $0.00000 | $0.00064 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
_engine 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 6d 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
Studio 内嵌文学工程内核
本文件保留 SKILL.md 路径是为了兼容正式任务包的 required reading。它属于 Studio 安装包,不代表需要安装或定位另一个 Skill 仓库。
操作宪法
- 正式工作只通过当前任务包推进。
- 只读取任务包列出的资料,以及 Studio 注入的当前用户创作方向。
- 只写入
expected_outputs,不得手写 CLI 应生成的流程产物。 - 不使用 debug waiver、maintainer mode 或跳审指令。
- 正文与正文修订必须由当前主 Agent 完成,subagent 只做机械辅助工作。
- Agent 输出必须经过 Studio 写回白名单和内嵌引擎门禁,聊天回复不代表任务完成。
- Canon 应用、正式晋升、发布与高风险变更必须等待对应审批。
创作要求
- 长篇创作先完成字数预算、剧情库存与章节义务。
- 场景开发必须经过上下文、角色推演、分支、编排、候选正文、审查、晋升、状态演化与 Canon 分类。
- 正文生成遵守挂载文风、标点、节奏衔接、读者体验和反 AI 腔约束。
- 最终交付过滤场景编号、审查痕迹、Canon 注释和流程信息。
What ships with it
60 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.
- agentread.yaml 253 B
- AGENTS.md 633 B
- docs/agentread/context-packs/bootstrap.md 424 B
- docs/agentread/context-packs/scene-generation.md 285 B
- docs/agentread/context-packs/style-engine.md 313 B
- docs/agentread/quickstart.md 1.7 KB
- docs/agentread/task-map.md 4.6 KB
- docs/architecture/agent-orchestration-plan.md 532 B
- docs/architecture/data-model.md 1.4 KB
- docs/architecture/knowledge-base-plan.md 846 B
- docs/architecture/memory-system.md 743 B
- docs/architecture/overview.md 1.1 KB
- docs/architecture/project-type-skill.md 2.5 KB
- docs/architecture/workflow-orchestration.md 525 B
- docs/architecture/workflow-platforms.md 625 B
- docs/implementation/phase1-initializer.md 289 B
- docs/implementation/phase10-workflow-runner.md 2.5 KB
- docs/implementation/phase11-api-langgraph-dify.md 2.6 KB
- docs/implementation/phase12-dify-dsl.md 1.8 KB
- docs/implementation/phase13-api-auth.md 1.3 KB
- docs/implementation/phase14-workflow-persistence.md 1.7 KB
- docs/implementation/phase15-approval-loop.md 1.2 KB
- docs/implementation/phase16-generation-provider.md 1.6 KB
- docs/implementation/phase17-knowledge-store.md 1.4 KB
- docs/implementation/phase18-style-eval.md 1.2 KB
- docs/implementation/phase19-canon-lint.md 1.4 KB
- docs/implementation/phase2-memory-context.md 345 B
- docs/implementation/phase20-branch-simulation.md 2.0 KB
- docs/implementation/phase20-character-background-story.md 1.5 KB
- docs/implementation/phase21-publish-chain.md 1.9 KB
- docs/implementation/phase22-scene-composer.md 4.5 KB
- docs/implementation/phase23-model-provider-prompt-pack.md 6.6 KB
- docs/implementation/phase24-character-state-evolution.md 2.8 KB
- docs/implementation/phase25-candidate-promotion-state-apply.md 4.3 KB
- docs/implementation/phase26-style-prompt-effectiveness.md 3.0 KB
- docs/implementation/phase27-agent-provider.md 3.4 KB
- docs/implementation/phase28-agent-schema-repair.md 1.2 KB
- docs/implementation/phase29-agent-scene-review.md 2.0 KB
- docs/implementation/phase3-style-compiler.md 187 B
- docs/implementation/phase30-agent-canon-review.md 826 B
- docs/implementation/phase31-agent-json-patch-plan.md 779 B
- docs/implementation/phase32-agent-style-prompt.md 971 B
- docs/implementation/phase33-agent-review-committee.md 897 B
- docs/implementation/phase34-agent-workflow-integration.md 1.5 KB
- docs/implementation/phase35-demo-regression.md 915 B
- docs/implementation/phase36-global-config-frontend.md 2.8 KB
- docs/implementation/phase37-asset-candidate-schemas.md 1012 B
- docs/implementation/phase38-agent-character-creation.md 561 B
- docs/implementation/phase39-agent-worldbuilding.md 491 B
- docs/implementation/phase4-scene-review-loop.md 577 B
- docs/implementation/phase40-agent-outline-creation.md 483 B
- docs/implementation/phase41-candidate-review-promotion.md 809 B
- docs/implementation/phase42-asset-workflow-modes.md 532 B
- docs/implementation/phase43-asset-api-frontend.md 541 B
- docs/implementation/phase44-asset-prompt-templates.md 502 B
- docs/implementation/phase45-asset-demo-regression.md 488 B
- docs/implementation/phase46-creative-director-agent.md 3.7 KB
- docs/implementation/phase47-frontend-api-key-config.md 1.6 KB
- docs/implementation/phase48-agent-auto-llm-provider.md 2.6 KB
- docs/implementation/phase5-roleplay-lab.md 946 B
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.
- 6d ago First seen · 21 lines · 0 tokens per session scan A ac0f17f41f69
_engine is a skill published in the GitHub repository o-1717986918/arcvellum (12 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 320 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-30.
Other skills, from other repositories
bump-version
This skill should be used when the user asks to "bump the version", "release a new version", "prepare a release", "update the version number", "version bump", or needs to determine and apply a semver version increment based on recent commits.
atifact
This skill should be used when the user asks to "extract agent trajectory", "convert HAR to trajectory", "get trajectory from session", "parse agent session", "convert Claude Code logs", "convert Copilot CLI logs", "extract ATIF", or needs to convert HAR files or JSONL session logs into ATIF trajectory JSON using the…
agent-flow
Design, validate, edit, visualize, and execute AgentFlow Markdown-first workflows with deterministic Boolean gates. Use when a task benefits from explicit boxes, arrows, branching, parallel work, resumable progress, or when the user asks to create/modify/run a workflow graph in AgentFlow.
ss-explore-source
Explore and explain an unfamiliar codebase for onboarding. Use when a developer joins a project, when asked to "understand the codebase", "explain the architecture", "how does this project work", "where is X handled", or before making changes in code you haven't seen yet. Produces a structured map of stack…
ss-review
Wrap up a finished change — self-review the diff, run the full test/lint gate, verify against acceptance criteria, update docs, then prepare commit/PR. Use after coding is done, when asked to "review my changes", "wrap up", "finalize", or "is this ready to merge". Final stage of the specship pipeline.
ss-spec
Read and fully understand a spec, ticket, PRD, or feature request before any planning or coding. Use when given requirements to implement, when asked to "understand this spec", "what does this ticket mean", or as the first step of a feature. Extracts goals, requirements, acceptance criteria, edge cases, and open…