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/agent0ai/space-agent/agentsgit clone --depth 1 https://github.com/agent0ai/space-agentWhat 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.04846 |
| Opus 5 | $0.00000 | $0.02423 |
| Sonnet 5 | $0.00000 | $0.00969 |
| Haiku 4.5 | $0.00000 | $0.00485 |
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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- AGENTS — 88% identical, 148 lines differ
How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Purpose
commands/ contains CLI command modules used by space.
Keep this file scoped to command-module behavior and help metadata. Repo-wide CLI surface and top-level command names still belong in /AGENTS.md.
This is a top-level DOX child doc. It owns the command-tree contract for commands/. If command-specific helper subtrees later grow their own AGENTS.md files, those local docs should own the implementation detail while this file stays focused on the command surface and conventions.
Documentation is top priority for this area. After any change to command discovery, command behavior, command help, or the command tree under commands/, update this file and the matching supplemental docs under app/L0/_all/mod/_core/documentation/docs/ in the same session before finishing.
Ownership
- Owns the documentation and operating contract for
/commands/. - Direct child DOX docs listed below own their narrower subtrees.
Local Contracts
Contract
Each command module should export:
execute(context)help
The help export may include:
namesummaryusagedescriptionargumentsoptionsexamples
The command loader discovers command modules dynamically from commands/*.js.
That means:
- every
.jsfile in this folder is treated as a command module - command names come from filenames
- command modules must stay import-safe because
helploads them dynamically to collect metadata - avoid top-level side effects, heavy startup work, or environment-specific initialization during import
- keep parsing and validation explicit inside the command module instead of relying on hidden global state
Non-command command-tree assets should stay out of commands/*.js. Shared helpers belong under subfolders such as commands/lib/, and command-owned metadata files such as commands/params.yaml should stay non-JavaScript so the loader does not treat them as commands.
commands/params.yaml is the command-owned schema for CLI-managed server config parameters. Each top-level key is the .env variable name, and each entry currently uses:
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.
- yesterday First seen · 457 lines · 0 tokens per session scan A 437e24101524
AGENTS is a command published in the GitHub repository agent0ai/space-agent (1,388 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,846 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.
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.