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/floomhq/moto/workplannpx skills add floomhq/moto --skill workplangit clone --depth 1 https://github.com/floomhq/motoWrote 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/floomhq/moto/workplan)<a href="https://agentmods.dev/skills/floomhq/moto/workplan"><img src="https://agentmods.dev/badge/skills/floomhq/moto/workplan.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.00089 | $0.00826 |
| Opus 5 | $0.00044 | $0.00413 |
| Sonnet 5 | $0.00018 | $0.00165 |
| Haiku 4.5 | $0.00009 | $0.00083 |
Grade A, and why
workplan 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 4d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Plan Skill
Work plans are timestamped markdown files that survive auto-compaction. They are the external brain for multi-step work.
File Convention
- Location: Project root, gitignored
- Name:
WORKPLAN-YYYYMMDD-slug.md(e.g.,WORKPLAN-20260228-auth-refactor.md) - One file per task/phase. Do not reuse old workplans. Start fresh for each distinct effort.
Actions
Create (/workplan or /workplan create)
- Read first. Before writing the plan, read all relevant files, issues, context.
- Ensure
.gitignoreincludesWORKPLAN-*.md(add if missing). - Create the file with this template:
# Work Plan: [Title]
Created: YYYY-MM-DD HH:MM
Last updated: YYYY-MM-DD HH:MM
Status: IN PROGRESS
## Context
[Why this work exists. The problem. Root cause. Key constraints. Links to issues/PRs.]
## Roadmap
- [ ] 1. Step description
- [ ] 2. Step description
- [ ] 3. Step description
## Decisions
[Log architectural or approach decisions with timestamps]
- [HH:MM] Chose X over Y because Z
## Discovered Issues
[Things found along the way that were not in the original scope]
- [HH:MM] Found ... while working on step 2
## Verification Log
[Each completed item gets a verification entry]
- [HH:MM] Step 1: VERIFIED - ran `npm test`, all 42 tests pass
- [HH:MM] Step 3: VERIFIED - manually tested login flow, works
Update (/workplan update)
- Read the active
WORKPLAN-*.mdfile(s) in the project root. - Update "Last updated" timestamp.
- Check off completed items with verification timestamps.
- Add any new discoveries or decisions.
- Report current status.
Close (/workplan close)
- Read the active workplan.
- Verify ALL items are checked off with verification timestamps.
- Run final verification (build, tests, manual checks).
- Change status to
DONE. - Add final summary:
## Completed
Closed: YYYY-MM-DD HH:MM
All N items implemented and verified. Build passes. Tests pass.
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.
- 4d ago First seen · 102 lines · 89 tokens per session scan A 1c5c9f082520
workplan is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 826 once invoked, about $0.0004 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-30.
Other skills, from other repositories
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
orchestrator-lanes
Claude Code dev-orchestrator only. File-based multi-lane PM playbook (score, DAG, run-controller, L0/L1/L2, ship). Use when this session IS that agent, or user says info / справка / lane-stack:orchestrator-lanes info. SKIP: Grok, Codex, Kimi, Qwen, AGY, Cursor writer CLIs and any default coding agent — do not load, do…
source-command-ccguide-daily
Daily update check — official Anthropic docs diff + guide/CC releases digest.
docs-maintain
Keep living docs/ honest after code changes. Use when: info, справка, lane-stack:docs-maintain info, nightly docs, docs-maintain, обновить документацию, актуализировать ARCHITECTURE.