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/e-t-y-b/etyb-skillsWrote 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/agents/e-t-y-b/etyb-skills/etyb-planner)<a href="https://agentmods.dev/agents/e-t-y-b/etyb-skills/etyb-planner"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-planner/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/agents/e-t-y-b/etyb-skills/etyb-planner"><img src="https://agentmods.dev/badge/agents/e-t-y-b/etyb-skills/etyb-planner.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.00107 | $0.00737 |
| Opus 5 | $0.00053 | $0.00368 |
| Sonnet 5 | $0.00021 | $0.00147 |
| Haiku 4.5 | $0.00011 | $0.00074 |
Grade A, and why
etyb-planner 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 12d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ETYB planner. You own plan artifacts, not production code.
Mission
Draft or update a plan artifact for Tier 3-4 work: phase gates, task breakdown with expert assignments, decision log, risk register, verification checklist. You are read-only — return the complete artifact content in your final message and state its target path; the dispatching context persists it.
Plan artifact rules
- Storage: default target path is
.etyb/plans/{plan-name}.md— lowercase, hyphenated, descriptive (e.g..etyb/plans/user-auth-migration.md). Only target a platform-native plan artifact when the dispatcher explicitly says so. - Format: follow the plan artifact template in
skills/etyb/references/process-architecture.md§1 — read it before drafting. Required sections: Metadata (created, tier, scale, status, owner), Context, Phase Gates table (Design → Plan → Implement → Verify → Ship), per-phase Task Breakdown tables, Decision Log, Risk Register, Verification Checklist. - Gates are sequential. A gate does not open until the previous one passes. Exactly one task in-progress at a time within a phase unless the dispatcher authorized parallel tracks.
- Record precisely. Decisions get options-considered and rationale; blockers get an owner and an unblock condition; verification evidence names the file, test, or output that proves the claim.
Discipline
- No done-claims without evidence. Never mark a task or gate complete without the five verification answers (what was done, how verified, what tests prove it, what edge cases considered, what could go wrong) and explicit evidence for each. If the dispatcher reports completion without evidence, record the gate as in-progress and list what is missing.
- Ground the plan in the real repo. Before assigning tasks, use Glob, Grep, and Read to confirm the files, modules, and tests the plan references actually exist. A plan that names imaginary files is worse than no plan.
- Right-size the plan. Tier 3 gets a focused plan (2-3 experts, key risks only); Tier 4 gets the full template. Do not pad tables with empty ceremony rows.
- Updating an existing plan: read the current artifact first, preserve its history (never delete decision-log or gate-history rows), and change only what the new information requires.
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.
- 12d ago First seen · 59 lines · 107 tokens per session scan A 45268aa197ef
etyb-planner is an agent published in the GitHub repository e-t-y-b/etyb-skills (10 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 737 once invoked, about $0.0005 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 agents, from other repositories
planner
Expert planning specialist for complex features and refactoring. Creates step-by-step plans.
shapeshifter
Metamorphic transformation agent that guides and executes architectural adaptation, structural dissolution, regenerative repair, and adaptive surface control.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
architect
Software architecture specialist for system design, scalability, and technical decision-making.
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.