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/pivotnpx skills add noahrasheta/director --skill pivotgit clone --depth 1 https://github.com/noahrasheta/directorWhat 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.00021 | $0.07284 |
| Opus 5 | $0.00010 | $0.03642 |
| Sonnet 5 | $0.00004 | $0.01457 |
| Haiku 4.5 | $0.00002 | $0.00728 |
Grade D, and why
director:pivot scanned grade D with 2 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 2d 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
- **Pivots are normal:** Changing direction is a sign of learning, not failure. Frame it positively. "Good call" not "At least we caught it". Never suggest the user should have known better or planned differently. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Delete the files and directories for pending items that were approved for removal in the delta. Use Bash for `rm -rf` on directories. How it starts
The opening of the file, as written. The whole thing — 706 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Director's pivot command. Your job is to help the user change direction for their project by understanding what they've already built, what they want to change, and how to update the gameplan to match.
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 steps below IN ORDER.
Step 1: Init + Vision + Gameplan checks
1a: 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 1b.
1b: Check for a vision
Read .director/VISION.md. Check whether it has real content beyond the default template.
Template detection: If the file contains placeholder text like > This file will be populated when you run /director:onboard, or italic prompts like _What are you calling this project?_, or headings with no substantive content beneath them (just blank lines, template markers, or italic instructions), the project has NOT been onboarded yet.
If VISION.md is template-only, say:
"Before pivoting, we need to know what you're pivoting FROM. Want to start with
/director:onboard? It only takes a few minutes to capture your vision."
Wait for the user's response. If they agree, proceed as if they ran /director:onboard.
Stop here if no vision.
1c: Check for a gameplan
Read .director/GAMEPLAN.md. Check whether it has real content beyond the default template.
Template detection: Check for these signals:
- The init template phrase:
This file will be populated when you run /director:blueprint - The placeholder text:
_No goals defined yet_ - Whether there are actual goal headings with substantive content beneath them (real goal names, descriptions, steps -- not just template markers)
If GAMEPLAN.md is template-only, say:
"You have a vision but no gameplan yet. Want to create one with
/director:blueprintfirst, or would you rather update your vision directly?"
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.
- 2d ago First seen · 706 lines · 21 tokens per session scan D df4ea5934576
director:pivot is a skill published in the GitHub repository noahrasheta/director (1 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 7,284 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 2 findings (subtle steering, recursive force delete). 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.