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/agents-inc/agents-inc/editgit clone --depth 1 https://github.com/agents-inc/agents-incWhat 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.10512 |
| Opus 5 | $0.00000 | $0.05256 |
| Sonnet 5 | $0.00000 | $0.02102 |
| Haiku 4.5 | $0.00000 | $0.01051 |
Grade A, and why
edit 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edit Command (Detailed)
Extracted from:
reference/commands/index.md(edit section) andreference/type-system.md(edit command types). See commands/index.md for the full commands reference.
File: src/cli/commands/edit.tsx
Purpose: Modify what is installed here, from one of two producers — the wizard, or a configuration shared from agentsinc.sh — and apply the difference. Outputs a styled change summary (chalk-colored +/-/~ lines for added/removed/changed skills, agents, origins, scopes) and a simplified completion message ("Done"). Change summary uses skill display names (from matrix) and scope labels ([G]/[P]). Global-to-project scope changes render as green + additions.
edit is also the one command that stands on both ends of the editor round trip: --ui mints an id for this installation and opens it in the browser, --from <id> applies a configuration back. The wire contract behind both is features/seed-contract.md.
Flags
static flags declares three flags — two public, one hidden.
| Flag | Type | Hidden | Description |
|---|---|---|---|
| --ui | boolean | no | default: false. Opens agentsinc.sh instead of the wizard — the id --from names, or this installation when --from names nothing. |
| --from | string | no | helpValue: "<id>". Apply a configuration shared from agentsinc.sh by its id, removing whatever it leaves out. Interactive and destructive — see below. |
| --project-setup | boolean | yes | Internal: this run continues an init project setup (materialise + register even on no-change). Key = EDIT_PROJECT_SETUP_FLAG ("project-setup"); set only by init's dashboard delegation. |
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 · 363 lines · 0 tokens per session scan A bf601e181bb9
edit is a command published in the GitHub repository agents-inc/agents-inc (8 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 10,512 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-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.