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 floomhq/moto --skill agentsgit 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/agents)<a href="https://agentmods.dev/skills/floomhq/moto/agents"><img src="https://agentmods.dev/badge/skills/floomhq/moto/agents/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/floomhq/moto/agents"><img src="https://agentmods.dev/badge/skills/floomhq/moto/agents.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.00057 | $0.00374 |
| Opus 5.5 | $0.00023 | $0.00150 |
| Sonnet 5.5 | $0.00011 | $0.00075 |
| Haiku 4.5 | $0.00006 | $0.00037 |
Grade A, and why
agents 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.
What it actually says
Agents: Scan Running Claude Sessions
Runs scan.sh to inspect all tmux sessions running Claude and report what each is doing.
Usage
bash ~/.claude/skills/agents/scripts/scan.sh # all sessions
bash ~/.claude/skills/agents/scripts/scan.sh floom # only floom/* sessions
bash ~/.claude/skills/agents/scripts/scan.sh openpaper # only openpaper/* sessions
What It Shows
Per session:
- Session name and start time
- Working directory and git branch
- Context usage (percentage of context window used)
- Mode (plan mode, accept edits, etc.)
- Current activity (spinner line showing what Claude is actively doing)
- Current task (bullet point showing tool/task in progress)
- Last user message (what the user asked)
How to Respond
- Run the scan with the relevant project filter
- Summarize what each session is doing in a table
- Identify gaps: what work is NOT being covered by any session
- Suggest isolated work that won't conflict with active sessions
Technical Notes
- Uses
tmux capture-paneto read screen content (most reliable method) - Filters sessions by checking
pstreefor claude processes - Parses the Claude Code status line for directory, context, and mode
- Optional project filter matches against session names
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 · 46 lines · 57 tokens per session scan A c72312ecf62d
agents is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 374 once invoked, about $0.0002 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-30.
Other skills, from other repositories
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…
issue-triage
3-phase issue backlog management with audit, deep analysis, and validated triage actions. Use when triaging GitHub issues, sorting bug reports, cleaning up stale tickets, or detecting duplicate issues. Args: 'all' to analyze all, issue numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit only.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
sandbox-unblock
Diagnostic protocol to run before reporting a sandbox blocker or asking for a configuration change. Eleven checks that eliminate false positives, then a report template the person holding the settings can act on. On one measured day, six of eight reported blockers turned out to be false, all from the same handful of…
self-assessment
Interactive skill assessment with personalized learning path generation.
review-pr
Perform a comprehensive code review of a pull request.