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.
git clone --depth 1 https://github.com/marcoguillermaz/TierwardWrote 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/commands/marcoguillermaz/tierward/readme)<a href="https://agentmods.dev/commands/marcoguillermaz/tierward/readme"><img src="https://agentmods.dev/badge/commands/marcoguillermaz/tierward/readme.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.1 | $0.00000 | $0.00350 |
| Opus 5 | $0.00000 | $0.00175 |
| Sonnet 5 | $0.00000 | $0.00070 |
| Haiku 4.5 | $0.00000 | $0.00035 |
Grade A, and why
README 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 8d 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
Custom Commands
Custom commands are reusable prompt templates you invoke with /command-name in Claude Code.
When to use commands vs skills vs rules
| Mechanism | Use when | Loaded |
|---|---|---|
| Commands (this dir) | Reusable prompts you run on demand (e.g. /review, /deploy-checklist) |
On invocation only |
Skills (.claude/skills/) |
Multi-step audit workflows with structured output | On invocation only |
Rules (.claude/rules/) |
Constraints that apply to every session automatically | Every session |
How to create a command
- Create a Markdown file in this directory:
.claude/commands/my-command.md - Write the prompt template as the file content
- Use
$ARGUMENTSto accept user input:/my-command some input here - Invoke with
/my-commandin any Claude Code session
Example
# .claude/commands/review.md
Review the following files for correctness, security issues, and adherence
to the project conventions in CLAUDE.md:
$ARGUMENTS
Output: a numbered list of findings with severity (critical / major / minor).
Usage: /review src/api/users.ts src/api/auth.ts
Tips
- Keep commands focused on a single task
- Reference project files (CLAUDE.md, rules) for context - Claude reads them automatically
- Commands in subdirectories work too:
.claude/commands/db/migrate-check.md→/db/migrate-check - Commands are project-specific and committed to git - the whole team can use them
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.
- 8d ago First seen · 41 lines · 0 tokens per session scan A a2e15a4c5b3d
README is a command published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 350 tokens. 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 commands, from other repositories
harness-audit
Audit this repository's AI harness maturity with the deterministic harness-score scanner.
setup
Set up codachi as your statusline.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
afo
Open feature worktree in terminal and start agent (shortcut for feature-open).
ai-review
AI code review of the staged git diff via the Claude API.