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/noahrasheta/director/ideasnpx skills add noahrasheta/director --skill ideasgit clone --depth 1 https://github.com/noahrasheta/directorWrote 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/noahrasheta/director/ideas)<a href="https://agentmods.dev/skills/noahrasheta/director/ideas"><img src="https://agentmods.dev/badge/skills/noahrasheta/director/ideas.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.00016 | $0.02840 |
| Opus 5 | $0.00008 | $0.01420 |
| Sonnet 5 | $0.00003 | $0.00568 |
| Haiku 4.5 | $0.00002 | $0.00284 |
Grade A, and why
director:ideas 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Director's ideas command (plural). Your job is to show the user their saved ideas, help them pick one, analyze its complexity, suggest a route, and execute or hand off accordingly.
Read these references for tone and terminology:
reference/plain-language-guide.md-- how to communicate with the userreference/terminology.md-- words to use and avoid
Follow all 5 steps below IN ORDER.
Step 1: Check for Director project
Check if .director/ exists.
If it does NOT exist, run the initialization script silently:
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/init-director.sh`
Continue to Step 2.
Step 2: Read and display ideas
Read .director/IDEAS.md.
Parse the file: skip the header (# Ideas) and the italic description line that starts with _Captured ideas. Every remaining non-blank line that starts with - **[ is an idea entry.
If $ARGUMENTS is provided (the user ran /director:ideas "dark mode"):
Skip the numbered list display. Instead, search the parsed idea entries for one that matches the argument text (case-insensitive substring match). If exactly one match is found, select it and jump directly to Step 4. If multiple matches are found, display only the matching ideas as a numbered list and ask the user to pick one. If no matches are found, say: "I didn't find an idea matching that. Here are your saved ideas:" and display the full numbered list as described below, then continue to Step 3.
If no idea entries are found, say:
"Your ideas list is empty. Capture ideas anytime with /director:idea "...""
Stop here if no ideas.
If idea entries exist, display them as a numbered list. For each entry:
- Extract the date from the
**[YYYY-MM-DD HH:MM]**timestamp -- use just the month and day (e.g., "Feb 8"). - Extract the idea text from after the
--separator. - Display as:
N. [idea text] ([abbreviated date])
Format the display like this:
Here are your saved ideas:
1. Add dark mode support for the entire app (Feb 8)
2. Change the submit button color to match the brand (Feb 8)
3. Maybe add a search feature? (Feb 7)
Which one interests you? (Pick a number, or say "none" to keep them saved.)
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 · 303 lines · 16 tokens per session scan A cb3539e11c25
director:ideas is a skill published in the GitHub repository noahrasheta/director (1 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 2,840 once invoked, about $0.0001 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
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-discuss-phase
Gather phase context through adaptive questioning before planning.
gsd-debug
Systematic debugging with persistent state across context resets.
gsd-capture
Capture ideas, tasks, notes, and seeds to their destination.
gsd-code-review
Review source files changed during a phase for bugs, security issues, and code quality problems.
gsd-config
Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile.