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 marcoguillermaz/Tierward --skill simplifygit 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/skills/marcoguillermaz/tierward/simplify)<a href="https://agentmods.dev/skills/marcoguillermaz/tierward/simplify"><img src="https://agentmods.dev/badge/skills/marcoguillermaz/tierward/simplify.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.00572 |
| Opus 5 | $0.00000 | $0.00286 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
simplify 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 7d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Applicability
Run on files changed in the current block after writing (Phase 2). Skip for trivial 1-file changes with <20 lines modified.
Input: the user invokes /simplify optionally followed by file paths. If no paths given, use git diff --name-only HEAD to find changed files. Filter to source files only (skip config, docs, generated files).
Step 1 - Scan each file for simplification opportunities
For every source file in scope, check these 6 patterns:
S1 - Early returns
Nested if/else where the else (or if) branch is a short return, throw, or continue. Invert the condition and return early to flatten the block.
S2 - Nesting depth
Any block nested >3 levels deep. Extract the inner logic into a named function, or apply guard clauses (S1) to reduce depth.
S3 - Local duplication
Two or more blocks within the same file that repeat the same logic (>3 lines identical or near-identical). Extract into a local helper.
S4 - Conditional simplification
- Ternaries nested inside ternaries
- Boolean expressions that can collapse (
if (x) return true; return false;→return x;) - Switch/match with identical arms that can be merged
S5 - Dead code
- Unreachable code after return/throw/break
- Commented-out code blocks (>3 lines)
- Unused local variables, parameters, or imports (only flag if confidence is high)
S6 - Magic values
Repeated literal values (strings, numbers) used >2 times in the same file. Extract to a named constant at file/module scope.
Step 2 - Apply fixes
For each finding:
- Apply the simplification directly using the Edit tool.
- Keep changes minimal - do not restructure surrounding code.
- Preserve existing tests - if a rename would break imports, skip it.
Step 3 - Summary
Output a compact summary:
/simplify - [N] files scanned, [M] changes applied
| File | Change | Pattern |
|---|---|---|
| path/to/file.ext | description of change | S1/S2/S3/S4/S5/S6 |
If no changes needed: /simplify - [N] files scanned, all clean ✓
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.
- 7d ago First seen · 68 lines · 0 tokens per session scan A 6a107e2cf574
simplify is a skill published in the GitHub repository marcoguillermaz/Tierward (4 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 572 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 skills, from other repositories
address-conductor-comment
A workflow for handling pending Conductor code-review comments, including reading their discussion and assigning changes to subagents when appropriate.
explain-comment
A skill that reads a specified file or code range and adds explanatory comments in Japanese. The comments use a question style and focus on important logic, design choices, and side effects.
build-feature
Full pipeline: evaluation -> spec -> implementation -> review -> QA.
cn-check
Install and run the Continue CLI (cn) to execute AI agent checks on local code changes. Use when asked to "run checks", "lint with AI", "review my changes with cn", or set up Continue CI locally.
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.
review
Adversarial fresh-context review of an increment before it ships. Every finding cites path:line and is re-verified. Use when saying "review", "grill this", or "critique the implementation".