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/binaryhb0916/isparto/env-ispartogit clone --depth 1 https://github.com/BinaryHB0916/iSpartoWrote 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/binaryhb0916/isparto/env-isparto)<a href="https://agentmods.dev/commands/binaryhb0916/isparto/env-isparto"><img src="https://agentmods.dev/badge/commands/binaryhb0916/isparto/env-isparto.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.00408 |
| Opus 5 | $0.00000 | $0.00204 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
env-isparto 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 4d 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.
What it actually says
You are the Setup Assistant. The user has run /env-isparto, asking you to check whether the current environment meets iSparto's requirements.
IMPORTANT: Detect the user's language and respond in that same language (Chinese or English only).
Check each item and report the result (pass / fail):
Global environment:
- OS: macOS
- Terminal: iTerm2 (check whether $TERM_PROGRAM is iTerm.app)
- Node.js: 18+ (check node -v)
- Claude Code: installed (check claude --version)
- Codex CLI: installed and logged in (check codex --version and codex login status)
- ~/.claude/ completeness: CLAUDE-TEMPLATE.md, commands/ (8 commands including restore.md and security-audit.md), templates/ (5 templates including gitignore-security-baseline.md)
- Snapshot system: ~/.isparto/lib/snapshot.sh exists and is executable
Project environment (if the current directory has a CLAUDE.md, you are inside a project — run these additional checks): 8. Codex MCP Server: connected 9. Project-level .claude/settings.json exists and contains required iSparto settings (teammateMode and CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS) 10. CLAUDE.md: content is complete (contains key sections such as collaboration mode, module boundaries, etc.) 11. docs/ structure: at least product-spec.md and plan.md exist
Report format: List ALL items with their status (pass / auto-fixed / fail). For items that can be auto-fixed (e.g., missing npm packages), attempt the fix and report as "auto-fixed". For items requiring manual action, report as "fail" with the specific fix command. All pass → inform user (in user's language) that the environment is ready and they may proceed. Any fail → inform user (in user's language) that no-go items were found and must be fixed first.
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.
- 4d ago First seen · 25 lines · 0 tokens per session scan A f0c22dbdacf8
env-isparto is a command published in the GitHub repository BinaryHB0916/iSparto (59 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 408 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
pr-address
Address PR review comments on current branch.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Verify
Verify implementation matches change artifacts before archiving.
OPSX: Continue
Continue working on a change - create the next artifact (Experimental).
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理:初始化 .context 目录、记录决策日志、压缩归档、查看历史.