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/nicholaspsmith/glancey/agentsgit clone --depth 1 https://github.com/nicholaspsmith/GlanceyWhat 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.00020 | $0.02760 |
| Opus 5 | $0.00010 | $0.01380 |
| Sonnet 5 | $0.00004 | $0.00552 |
| Haiku 4.5 | $0.00002 | $0.00276 |
Grade A, and why
agents 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 — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agents — Parallel Agent Orchestrator
You are the orchestrator. You will launch 1-10 parallel Claude Code agents, each working autonomously on a beads task in its own git worktree. Follow these phases exactly.
Arguments: $ARGUMENTS
Phase 1 — Parse Arguments & Fetch Tasks
Parse the following flags from $ARGUMENTS (all optional):
| Flag | Default | Description |
|---|---|---|
--auto-merge |
off | Agents auto-merge PRs after CI passes |
--count N |
(interactive) | Max number of tasks to select |
--model MODEL |
sonnet |
Model for spawned agents (ignored when --agent is set, since the agent definition specifies its own model) |
--budget N |
5 |
Max USD per agent |
--agent NAME |
(none) | Use an existing agent definition from .claude/agents/NAME.md. Multiple instances of the same agent run concurrently — the file is a reusable template, not a per-instance resource. |
Fetch tasks
First, check if bd (beads) is available:
command -v bd
If bd is available, fetch tasks:
bd ready --json
Then continue to Phase 2 with the beads task list.
If bd is NOT available (or returns no tasks), offer a manual task mode. Ask the user to describe the tasks they want agents to work on. Accept a list of task descriptions, one per agent. For example:
No beads tasks found. You can specify tasks manually.
How many agents do you want to launch? Enter task descriptions (one per line, empty line to finish):
1. Fix the login page redirect bug
2. Add unit tests for the payment module
3. Refactor the database connection pool
For manual tasks, generate synthetic task IDs (e.g., TASK-1, TASK-2, etc.) and use the descriptions as both the title and description in later phases.
Phase 2 — Select Tasks
If using beads tasks, present them as a numbered list:
Available tasks:
1. [BD-123] Fix auth token refresh logic
2. [BD-456] Add pagination to /api/users
3. [BD-789] Update error messages for form validation
...
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 · 345 lines · 20 tokens per session scan A f4cc39f9dc87
agents is a command published in the GitHub repository nicholaspsmith/Glancey (1 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 2,760 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.