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/maximumsoft-co-ltd/claude-flightdeck/ideanpx skills add Maximumsoft-Co-LTD/claude-flightdeck --skill ideagit clone --depth 1 https://github.com/Maximumsoft-Co-LTD/claude-flightdeckWrote 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/maximumsoft-co-ltd/claude-flightdeck/idea)<a href="https://agentmods.dev/skills/maximumsoft-co-ltd/claude-flightdeck/idea"><img src="https://agentmods.dev/badge/skills/maximumsoft-co-ltd/claude-flightdeck/idea.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.00106 | $0.01302 |
| Opus 5 | $0.00053 | $0.00651 |
| Sonnet 5 | $0.00021 | $0.00260 |
| Haiku 4.5 | $0.00011 | $0.00130 |
Grade A, and why
idea 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 — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/idea — Structured Idea Capture & Promotion
Announce: Using /idea to [capture / refine / promote] …
Discovery is the staging area: ideas live in docs/project/ideas/D###-<slug>.md
until they pass the DoR gate; only then do they become rows in
docs/project/backlog.md. /work is where backlog items become sprint tasks.
ID rules: ../../../docs/project/NAMING.md.
Token budget
- Never full-Read
backlog.mdor board files — useGrepfor duplicate scans. - Read an existing idea detail file only when refining or promoting that D###.
- Keep the interview lean — short, targeted questions per stage; no exhaustive checklists. Read only the target idea file in full at promote time.
Modes
/idea <text> — Capture a raw idea
- Stage 1 — Core: title, problem statement, affected user roles, source, affected components / services.
- Estimate complexity — trivial/small → 3-4 follow-ups; medium → 5-8; large → 8-10. Don't over-ask small items.
- Stage 2 — Scope: target behaviour, explicit non-goals, related features, cross-component impact (events, persistence, UI entry points).
- Stage 3 — Context: urgency, technical constraints, deadlines, related ideas.
- Allocate the next D### ID —
Grep docs/project/ideas/for the highest existing D### and increment. Sequential, never reused. - Duplicate scan —
Grep docs/project/ideas/+docs/project/backlog.mdfor title keywords. Surface any match and ask whether to merge before creating. - Create the detail file
docs/project/ideas/D###-<slug>.mdwith: User Stories, Acceptance Criteria (≥3 aimed at), Affected Components, Cross-cutting Concerns (multi-tenancy / RBAC / observability as applicable), Open Questions. State =raw. - Confirm — print the D### assigned and the file path.
Ideas can be
dropped(state change in the file header) but the file is never deleted — keep the trail.
/idea refine D### — Fill gaps on an existing idea
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 · 104 lines · 106 tokens per session scan A d6f1880e872c
idea is a skill published in the GitHub repository Maximumsoft-Co-LTD/claude-flightdeck (2 stars, last pushed 2mo ago), licensed MIT. It adds 106 tokens to every session and 1,302 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 skills, from other repositories
github-issue-triage
Issue triage and lifecycle management agent for ZeroClaw. Use this skill whenever the user wants to: triage open issues, close stale/duplicate/fixed issues, apply labels, run a backlog sweep, enforce the current issue stale policy, or handle a specific issue. Trigger on: 'triage issues', 'issue triage', 'sweep…
things-mac
Manage Things 3 via the things CLI on macOS (add/update projects+todos via URL scheme; read/search/list from the local Things database). Use when a user asks Otto to add a task to Things, list inbox/today/upcoming, search tasks, or inspect projects/areas/tags.
flowai-team-dashboard
三个 tab 的团队管理后台: 成员、详情、活动日志, 含图表 + CSV 导出.
review-offered-task
Review a task that has been offered to you and decide whether to accept or reject it.
close-issue
Close a GitHub or GitLab issue with a summary comment.
seeds-issue-audit
Audit and triage open Seeds (sd) issues — find which can be closed, auto-close high-confidence completed ones, and report borderline cases. Activate for prompts like "audit open issues", "which seeds issues can be closed", "clean up the issue tracker", "triage the seeds backlog".