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 skills add stuartshields/claude-setup --skill block-journeygit clone --depth 1 https://github.com/stuartshields/claude-setupWrote 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/stuartshields/claude-setup/block-journey)<a href="https://agentmods.dev/skills/stuartshields/claude-setup/block-journey"><img src="https://agentmods.dev/badge/skills/stuartshields/claude-setup/block-journey/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/stuartshields/claude-setup/block-journey"><img src="https://agentmods.dev/badge/skills/stuartshields/claude-setup/block-journey.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01816 |
| Opus 5.5 | $0.00014 | $0.00726 |
| Sonnet 5.5 | $0.00007 | $0.00363 |
| Haiku 4.5 | $0.00003 | $0.00182 |
Grade A, and why
block-journey 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 1mo 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: block-journey
When to Use
Run /block-journey <name> to document how a block or component works from two perspectives: the editor creating content, and the visitor consuming it. Use when onboarding to an unfamiliar block, before modifying one, or after building one to capture its contracts.
Parse $ARGUMENTS to extract the block name and an optional path scope:
accordion— search the entire working directory for a block named "accordion"rte-blocks/accordion— search only within directories whose path contains "rte-blocks" for "accordion"mu-plugins/rtm-blocks/faq— search only within directories whose path contains "mu-plugins/rtm-blocks" for "faq"
If $ARGUMENTS contains a /, treat everything before the last / as a path substring filter and everything after as the block name. Match the filter against the full directory path, not just the immediate parent. This matters when the same plugin name exists under different parent directories (e.g., plugins/rtm-blocks vs mu-plugins/rtm-blocks). If no /, treat the entire argument as the block name and search broadly.
When the path filter matches multiple locations, list them and ask the user which one to document.
If $ARGUMENTS is empty, ask the user which block or component to document.
Do NOT modify any source files. This is documentation, not implementation.
Method
Step 1: Discover Files
Search the working directory for all files related to the block name from $ARGUMENTS. Do not assume a specific file structure — discover what exists.
Look for:
- Registration files — block metadata, config, or schema (JSON, YAML, PHP, JS)
- Editor files — edit components, sidebar controls, inspector panels, editor styles
- Save / render files — save components (static blocks), PHP render callbacks, server-side templates
- Front-end behaviour — JS that runs on page load for interactivity (toggles, carousels, modals, tabs)
- Styles — CSS/SCSS for both editor and front-end
- Shared components — any reusable pieces the block imports or depends on
- Template partials — theme-side templates that render the block's output
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.
- 1mo ago First seen · 168 lines · 34 tokens per session scan A ba7529794239
block-journey is a skill published in the GitHub repository stuartshields/claude-setup (2 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 1,816 once invoked, about $0.0001 per session on Opus 5.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
setup
First-time setup for a new user of this job application generator. Builds the user's masterdata.yaml (from their existing CV/resume file or by interview), sets their output file prefix, and personalizes rules.md. Use when the user says "setup", "set me up", "configure for me", "I just cloned this", or when…
debug
Instrument web/web-app code with structured debug logging via a global variable (window.debuglogs). Produces a clean JSON timeline for reproducing and diagnosing bugs. Use when user wants to debug a feature or track down a bug.
feature-plan
Create detailed implementation plans for features. Asks clarifying questions, suggests solutions, proposes architecture, and outputs a structured plan document. Use when user wants to plan a feature before coding.
frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
code-review
Perform thorough code reviews focusing on unused code, duplications, coding patterns, bugs, and optimizations. Use when user wants code reviewed or audited. Read-only - outputs findings without making changes.
handoff
Capture current work context for handoff to another agent/developer. Gathers git state, todos, and modified files into a structured handoff document saved to the related spec folder.