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-rules-exnpx skills add atman-33/workhub --skill setup-rules-exgit 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-rules-ex)<a href="https://agentmods.dev/skills/atman-33/workhub/setup-rules-ex"><img src="https://agentmods.dev/badge/skills/atman-33/workhub/setup-rules-ex.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.00049 | $0.00612 |
| Opus 5 | $0.00024 | $0.00306 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
setup-rules-ex 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scaffold the two files that enable the rules-ex extended-rules system for this
project. Both files are templates — they will not be overwritten if they already
exist. The canonical template content lives in this skill's assets/templates/
folder (also used by the setup-all skill's Phase 4 — treat it as the single
source of truth and edit it there, not inline in either SKILL.md).
What gets created:
.claude/rules/rules-ex-authoring.md— a native path-scoped rule that auto-injects an authoring guide whenever you Read/Edit a file under.claude/rules-ex/. Required so the guide fires for the current repo (native.claude/rulesfiles only govern the repo they live in)..claude/rules-ex/README.md— explains what therules-exfolder is and how to author rules in it. Has nopaths:front matter intentionally, so the hook ignores it.
Steps
-
Read
.claude/rules/rules-ex-authoring.md.- If it already exists, display its path and current contents, then note it was left unchanged.
- If it does not exist, read
assets/templates/rules-ex-authoring.md(in this skill's folder) and write its exact contents to.claude/rules/rules-ex-authoring.md.
-
Read
.claude/rules-ex/README.md.- If it already exists, display its path and current contents, then note it was left unchanged.
- If it does not exist, read
assets/templates/rules-ex-readme.md(in this skill's folder) and write its exact contents to.claude/rules-ex/README.md.
Output Format
Print a summary table after completing both steps:
| File | Status |
|---|---|
.claude/rules/rules-ex-authoring.md |
created / already existed |
.claude/rules-ex/README.md |
created / already existed |
Then remind the user:
- Add your own cross-cutting rules as
*.mdfiles under.claude/rules-ex/. Each file must have apaths:front matter (workspace-relative globs) — see the authoring guide that auto-injects when you edit files there. - The
inject-extended-ruleshook fires on Read/Edit/Write; rules take effect immediately in the current session without a restart.
What ships with it
2 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.
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 · 57 lines · 49 tokens per session scan A df24f096c30c
setup-rules-ex is a skill published in the GitHub repository atman-33/workhub (2 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 612 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
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…
superbrain-distill
Internal SuperBrain skill — run by the detached capture child to distill a session-event delta into routed Obsidian notes. Not for direct user invocation.
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…
memo-writing
How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on /memex:save, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the [memex] activity nudge appears in context. Do NOT trigger for…
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…
trellis-break-loop
Deep bug analysis to break the fix-forget-repeat cycle. Analyzes root cause category, why fixes failed, prevention mechanisms, and captures knowledge into specs. Use after fixing a bug to prevent the same class of bugs.