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 commands/b33eep/claude-code-setup/with-advisorgit clone --depth 1 https://github.com/b33eep/claude-code-setupWhat 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.00000 | $0.02335 |
| Opus 5 | $0.00000 | $0.01167 |
| Sonnet 5 | $0.00000 | $0.00467 |
| Haiku 4.5 | $0.00000 | $0.00233 |
Grade A, and why
with-advisor 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 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.
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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
With Advisor: Expert Pair Programming
Spawn expert advisor(s) that monitor your work and give proactive domain feedback. You stay in control — advisors supplement your judgment.
Usage
/with-advisor "implement OAuth login with JWT tokens"
/with-advisor "optimize the slow database queries"
/with-advisor "design a plugin system for the CLI"
Tasks
1. Validate arguments
The command requires a task description.
No arguments:
Usage: /with-advisor "task description"
Example: /with-advisor "implement OAuth login with JWT tokens"
Stop here. Do not proceed.
2. Assess task complexity
If the overhead of spawning advisors exceeds the benefit, refuse:
Task is too simple for advisors. Just do it directly.
Stop here. Do not proceed. Otherwise, continue.
3. Select advisor expertise
Analyze the task and decide which advisor expertise adds value. Think about:
- What domain knowledge would catch mistakes you'd miss?
- What expertise would improve the design, not just the code?
Rules:
- Max 2 advisors
- Only spawn a second if genuinely different expertise is needed
- Frame advisors around the problem being solved, not the tool being built
Examples:
| Task | Advisors | Why |
|---|---|---|
| "implement OAuth login" | Security Expert, Auth Domain Expert | Security-sensitive, unfamiliar domain |
| "optimize database queries" | Performance Expert | Specific domain expertise |
| "refactor the auth module" | Codebase Patterns Expert | Large change, consistency matters |
| "add WebSocket support" | Distributed Systems Expert | Real-time, concurrency concerns |
| "migrate to TypeScript" | TypeScript Migration Expert | Large scope, many gotchas |
4. Create team and spawn advisors
Use Agent Teams (TeamCreate + Task tool) to spawn each advisor.
Team setup:
- Team name:
advisor-session(or similar short name) - Create tasks for tracking
- If a team named
advisor-sessionalready exists (user ran/with-advisorbefore), ask: "Advisors from a previous session are still active. Replace them with new advisors? [Yes / No]". If Yes, shut down existing advisors first (SendMessage withtype: shutdown_request), delete the team, then create a new one. If No, stop here.
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 · 288 lines · 0 tokens per session scan A 5fd78955a7da
with-advisor is a command published in the GitHub repository b33eep/claude-code-setup (56 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,335 tokens. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.