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/atman-33/workhub/setup-allnpx skills add atman-33/workhub --skill setup-allgit clone --depth 1 https://github.com/atman-33/workhubWrote 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/atman-33/workhub/setup-all)<a href="https://agentmods.dev/skills/atman-33/workhub/setup-all"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/setup-all.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 | $0.00029 | $0.00765 |
| Opus 5 | $0.00015 | $0.00382 |
| Sonnet 5 | $0.00006 | $0.00153 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
setup-all 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run all engineering plugin setup steps in sequence. Each phase is independent — a failure in one phase is reported and the next phase continues.
Phase 1 — Set up OpenSpec
- Run
node --version. If Node.js is missing or older than 20.19.0, report the version and skip to Phase 2 with a note. - Check whether OpenSpec CLI is already installed globally:
If not installed, install it:npm list -g @fission-ai/openspec --depth=0npm install -g @fission-ai/openspec@latest - Run:
openspec init --tools claude
Phase 2 — Scaffold project-context.json
- Read
.claude/project-context.jsonin the current project root.- If it already exists: show its current contents and note that it was left unchanged.
- If it does not exist: create it with the following template (placeholder paths must be replaced by the user):
{ "roleBasedDelegation": true, "openspecPath": "<absolute path to the openspec docs folder>", "projects": [ { "name": "example-project", "path": "<absolute path to a frequently-used project>", "summary": "short one-line description (optional)" } ] }
Phase 3 — Scaffold rules-ex infrastructure
-
Read
.claude/rules/rules-ex-authoring.md.- If it already exists: show its path and note it was left unchanged.
- If it does not exist: read
skills/setup-rules-ex/assets/templates/rules-ex-authoring.md(relative to this plugin's root; the canonical template, shared with thesetup-rules-exskill) and write its exact contents to.claude/rules/rules-ex-authoring.md.
-
Read
.claude/rules-ex/README.md.- If it already exists: show its path and note it was left unchanged.
- If it does not exist: read
skills/setup-rules-ex/assets/templates/rules-ex-readme.md(relative to this plugin's root) and write its exact contents to.claude/rules-ex/README.md.
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.
- 3d ago First seen · 83 lines · 29 tokens per session scan A 89ed90c1aecc
setup-all is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 765 once invoked, about $0.0001 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
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
memory
Use this skill when Pioneer should proactively use durable memory or recalled context: decide whether memory can improve a turn, answer from remembered user/project facts, request memory tools, search/list/get stored memories, save durable preferences or project decisions, forget memories, audit or clean up memory, or…
subagents
Use this skill when Pioneer should delegate current-turn work to attached task-backed subagents, coordinate parallel child agents, wait for child results, review/revise/accept/cancel/detach attached work, or synthesize accepted child results into the parent answer.
writing-staffing
Dispatch reference for composing writing teams. Teaches which extra skills to attach via --skills, which resources to reference in spawn prompts, and when to fan out versus run parallel lanes. Load when staffing a workflow.
trellis-meta
Understand and customize the local Trellis architecture inside a user project. Use when modifying .trellis plus platform hooks, settings, agents, skills, commands, prompts, workflows, the channel runtime (trellis channel), bundled runtime agents under .trellis/agents/, selectable workflow templates, registry-backed…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…