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/khanh-vu/claude-force/pick-agentgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/commands/khanh-vu/claude-force/pick-agent)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/pick-agent"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/pick-agent.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.00008 | $0.02712 |
| Opus 5 | $0.00004 | $0.01356 |
| Sonnet 5 | $0.00002 | $0.00542 |
| Haiku 4.5 | $0.00001 | $0.00271 |
Grade A, and why
pick-agent 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 5d 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 — 495 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pick Agent Command
Copy agent packs (definitions + contracts) from a source project to your target project.
Purpose
The /pick-agent command helps you:
- Browse available agents from claude-force or another project
- Copy agent definition files to your project
- Copy agent contract files to your project
- Update your claude.json configuration automatically
- Reuse proven agent packs across projects
Usage
List Available Agents
/pick-agent --list
Copy Single Agent
/pick-agent python-expert
Copy Multiple Agents
/pick-agent python-expert code-reviewer database-architect
Specify Source Project
/pick-agent python-expert --source /path/to/claude-force
Copy from Different Project
/pick-agent python-expert --source /path/to/other-project --target /path/to/my-project
What Gets Copied
For each agent, the command copies:
-
Agent Definition:
agents/{agent-name}.md- Role and responsibilities
- Skills and specializations
- Deliverables format
- Examples and patterns
-
Agent Contract:
contracts/{agent-name}.contract- Scope of authority
- Core responsibilities
- Input/output requirements
- Quality gates
- Collaboration protocol
-
Configuration Entry: Updates
claude.json- Agent metadata
- File references
- Domain tags
- Priority level
Implementation
You should execute this command by:
- Import the PickAgentCommand class:
from claude_force.commands.pick_agent import PickAgentCommand
from pathlib import Path
-
Determine source and target paths:
- Source: claude-force installation or another project
- Target: Current project or user-specified path
- Default source: claude-force package location
- Default target: Current working directory
-
List available agents:
command = PickAgentCommand(
source_project=Path("/path/to/claude-force"),
target_project=Path("/path/to/my-project")
)
# List all available agents
available = command.list_available_agents()
print(f"Available agents: {', '.join(available)}")
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.
- 5d ago First seen · 495 lines · 8 tokens per session scan A 1eb40c2b11fe
pick-agent is a command published in the GitHub repository khanh-vu/claude-force (5 stars, last pushed 9mo ago), licensed MIT. It adds 8 tokens to every session and 2,712 once invoked, about $0.0000 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
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.