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/tatargabor/set-copilot/helpgit clone --depth 1 https://github.com/tatargabor/set-copilotWrote 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/tatargabor/set-copilot/help)<a href="https://agentmods.dev/commands/tatargabor/set-copilot/help"><img src="https://agentmods.dev/badge/commands/tatargabor/set-copilot/help.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.00000 | $0.01394 |
| Opus 5 | $0.00000 | $0.00697 |
| Sonnet 5 | $0.00000 | $0.00279 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
help 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 today.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When the user asks about set-core features, use this quick reference to answer. For deeper details, read the linked files or run set-<command> --help.
CLI Commands
| Command | Description |
|---|---|
set-new <change-id> |
Create a git worktree for a spec change |
set-list |
List active worktrees for projects |
set-work <change-id> |
Open editor for a worktree (creates if needed) |
set-close <change-id> |
Remove a worktree and optionally its branch |
set-merge <change-id> |
Merge a worktree's branch into a target branch |
set-status |
Display worktree and Claude agent status |
set-loop <command> |
Run autonomous agent loop in a worktree |
set-memory <command> |
Per-project cognitive memory (shodh-memory). Details: docs/developer-memory.md |
set-control |
Launch the Control Center GUI |
set-project <command> |
Project management (init, deploy) |
set-openspec <command> |
OpenSpec CLI wrapper (status, init, update) |
set-usage |
Show Claude API usage and burn rate |
set-config <command> |
Configure set-core settings |
set-add [path] |
Add an existing git repo to set-core |
set-focus <change-id> |
Focus the editor window for a worktree |
set-run-logs <run-id> |
Forensic analysis of a completed orchestration run (discover/digest/session/grep/orchestration) |
set-version |
Display set-core version |
Skills (Slash Commands)
OpenSpec Workflow (/opsx:*)
| Skill | Description |
|---|---|
/opsx:new |
Start a new change with structured artifacts (proposal → design → specs → tasks) |
/opsx:ff |
Fast-forward: create all artifacts in one go, ready for implementation |
/opsx:apply |
Implement tasks from a change |
/opsx:continue |
Continue working on a change — create the next artifact |
/opsx:verify |
Verify implementation matches change artifacts |
/opsx:archive |
Archive a completed change (syncs specs, cleans up) |
/opsx:bulk-archive |
Archive multiple completed changes at once |
/opsx:explore |
Open-ended thinking/exploration mode (no implementation) |
/opsx:sync |
Sync delta specs from a change to main specs |
/opsx:onboard |
Guided walkthrough of the OpenSpec workflow |
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.
- today First seen · 119 lines · 0 tokens per session scan A 55fcf47fd226
help is a command published in the GitHub repository tatargabor/set-copilot (2 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,394 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-09-04.
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.
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.