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/issuenpx skills add floomhq/moto --skill issuegit clone --depth 1 https://github.com/floomhq/motoWhat 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.00062 | $0.00654 |
| Opus 5 | $0.00031 | $0.00327 |
| Sonnet 5 | $0.00012 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
issue 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 3d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Issue Management
Manage GitHub issues across multiple accounts. Always use GitHub Issues, never ISSUES.md files.
Step 1: Detect Project and Switch Account
Determine which project from context (cwd, user mention). If ambiguous, ask.
| Project | Account alias | Repo |
|---|---|---|
| project-a | gh-project-a |
auto-detect from cwd |
| project-b | gh-project-b |
org/repo-name |
| personal | gh-personal |
auto-detect from cwd |
Check current account first:
gh auth status
Switch to correct account before any gh command.
Step 2: Execute the Right Command
Create Issue
gh issue create --title "..." --label "LABELS" --body "BODY"
For projects with strict labeling: ALWAYS include required labels. Ask the user for priority if not provided.
For repos you're not in the directory of:
gh issue create --repo org/repo-name --title "..." --body "..."
List Issues
gh issue list --state open
gh issue list --label "P0" --state open
gh issue list --label "P0,frontend" --state open
View Issue
gh issue view 123
Close Issue
Always close with a comment explaining the resolution:
gh issue close 123 --comment "Fixed in commit abc123. Verified on live site."
Label Conventions
Example: Priority + Area labeling
| Type | Labels |
|---|---|
| Priority | P0 (critical), P1 (high), P2 (medium), P3 (low) |
| Area | frontend, backend, pipeline |
Always include one from each group. If user doesn't specify priority, ask.
Issue Body Format
For bug reports:
**Steps to reproduce:**
1.
2.
**Expected:**
**Actual:**
**Context:** [URL, env, user account if relevant]
For feature requests:
**Problem:**
**Proposed solution:**
**Acceptance criteria:**
- [ ]
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.
- 3d ago First seen · 119 lines · 62 tokens per session scan A e7c5833ef800
issue is a skill published in the GitHub repository floomhq/moto (32 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 654 once invoked, about $0.0003 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
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
agent-workspace-linux
Use when a task needs an isolated hidden Linux desktop or workspace-owned browser: GUI app QA, web/browser/shopping automation, sandboxed app observation, or stale workspace cleanup. Routes agent-workspace-linux MCP tools on demand. Does NOT apply to host desktop/Chrome control, generic MCP setup, or pure code/file…
ss-component
Generate a new UI component following the StyleSeed design conventions.
loongsuite-pilot-insight
基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用；包含 AI Coding 事件表语义，以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE，通常与 sls-dashboard-builder 一起使用。.
map-review
Interactive 4-section code review using monitor, predictor, and evaluator agents plus the user and maintainer role reviewers on current changes. Use when reviewing a diff, PR, or staged work before merge. Do NOT use to plan or implement; use map-plan or map-efficient.
runjam-defaults
Default constraints for every RunJam session. Defines output path conventions, dependency checking rules, fallback strategies, and file management discipline. This skill is auto-injected into every session — do not remove. Current session working directory: /Users/guizhan/work/code/runjam.