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/tph-kds/deckforge/deckforge-runtime-plannernpx skills add tph-kds/deckforge --skill deckforge-runtime-plannergit clone --depth 1 https://github.com/tph-kds/deckforgeWhat 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.00038 | $0.00289 |
| Opus 5 | $0.00019 | $0.00144 |
| Sonnet 5 | $0.00008 | $0.00058 |
| Haiku 4.5 | $0.00004 | $0.00029 |
Grade A, and why
deckforge-runtime-planner 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
DeckForge Runtime Planner
Read ../../docs/ARCHITECTURE.md, ../../docs/RUNTIME_CONTRACT.md, ../deckforge/assets/deck-project.schema.json, and the relevant editor, presenter, security, performance, and publishing workflows.
Inspect the target organization, repository, deployment platform, identity model, data boundaries, and expected scale. Produce a concrete architecture with component boundaries, request and event flows, state ownership, APIs, persistence models, asset storage, authorization checks, versioning, collaboration semantics, publishing and embed policy, observability, migrations, backup and recovery, tests, and rollout phases.
Keep the serializable deck domain separate from ephemeral editor state. Keep editor, presenter, rendering, delivery, and background-processing concerns independently testable. Make assumptions, trade-offs, failure modes, and rejected alternatives explicit. Include how schema evolution, concurrent edits, autosave, optimistic updates, offline recovery, CDN caching, rendering performance, and revocation are handled.
This skill plans rather than implements. It must not invent infrastructure that conflicts with an existing coherent platform, and it must not place secrets, authorization decisions, or untrusted HTML inside DeckProject content.
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 · 16 lines · 38 tokens per session scan A baf77e522915
deckforge-runtime-planner is a skill published in the GitHub repository tph-kds/deckforge (4 stars, last pushed 16d ago), licensed MIT. It adds 38 tokens to every session and 289 once invoked, about $0.0002 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
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
image-generation
Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.
podcast-generation
Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.
vercel-deploy
Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.
engineer-system-change
Evaluate and carry out non-trivial software-system changes from first principles. Use when assessing RFCs, issues, designs, features, refactors, migrations, dependency changes, or proposed fields, events, APIs, modules, and services whose need, consumers, system fit, validation, or rollback require scrutiny. Read the…
skill-reviewer
Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.