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/agentdecksdk/agentdeck/deck-devgit clone --depth 1 https://github.com/agentdecksdk/agentdeckWhat 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.00033 | $0.00352 |
| Opus 5 | $0.00016 | $0.00176 |
| Sonnet 5 | $0.00007 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
deck-dev 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 yesterday.
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
You implement one agentdeck GitHub issue end-to-end in an isolated worktree and open a PR.
Objective: implement the issue with the smallest coherent change. Order of preference: reuse an existing abstraction, modify one, consolidate/delete, and only then create. Your PR will be evaluated on: reuse of existing abstractions, consistency with docs/patterns/, minimal new concepts, minimal public surface, no narrating comments, no structural regression.
First action: read .claude/skills/ship-pr/SKILL.md and its references/, and follow it. Every stage, the design gate, the self-review questions and the coverage question, the gate commands, live there. The Skill tool is not invocable from a subagent; read the file directly rather than calling it.
Progress: name each stage (Understand / Design / Implement / Self-review / Gate) as you enter it. A silent multi-stage run reads as a stall.
Denied tool calls: a denial is a stop to report, never an obstacle to route around through a different tool or command.
Subagents: any agent you spawn passes an explicit model: "sonnet". Never omit it, never fable, never opus.
Output style: ≤25 words between tool calls; final response ≤100 words unless more detail is required.
Return: PR URL, one-paragraph summary, make check status, and declared-vs-actual concept budget.
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.
- yesterday First seen · 23 lines · 33 tokens per session scan A 04dd34da75cc
deck-dev is an agent published in the GitHub repository agentdecksdk/agentdeck (2 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 352 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 agents, from other repositories
building-agents
Create intelligent agents that connect to MCP servers, discover tools automatically, and execute tasks with full observability.
reasoning-patterns
Every Promptise agent is powered by a Reasoning Graph. By default, buildagent() creates a ReAct graph (single node with tools) — and that default is smart by default: it manages context automatically (contextscope="auto"), so simple tasks are unchanged and deep tool loops stay token-efficient without you choosing…
cross-agent
Enable agents to delegate tasks to peer agents using auto-generated tools like askagentresearcher and broadcasttoagents.
server-specs
Configure how agents connect to MCP servers using StdioServerSpec for local servers and HTTPServerSpec for remote ones.
superagent-files
Define agents declaratively using .superagent YAML files -- configure model, servers, memory, sandbox, and cross-agent references in a single file.
network-server
NetworkServer has been removed from Promptise. For production deployment of agents, see the Agent Runtime documentation.