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/fatihguner/foreman/solo-commandgit clone --depth 1 https://github.com/fatihguner/foremanWhat 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.02222 |
| Opus 5 | $0.00000 | $0.01111 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
solo-command 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 3d 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Solo Command
Activates, deactivates, and inspects solo mode — the system-wide adaptation layer for solopreneurs.
/solo
Description
Activates solo mode. Writes mode: solo to the identity layer of memory and loads the solo configuration files (solo/SOLO.md, solo/solo-skill-relevance.yaml, solo/solo-audience-map.yaml, solo/solo-adaptations.yaml). From this point forward, every interaction is filtered through the solo lens until explicitly deactivated.
Activation triggers the following immediate changes:
- Skill relevance scoring adjusts routing priority for all 158 skills.
- Audience mapping remaps investor, board, and team outputs.
- Diagnostic adaptations skip or reframe 8 of 20 diagnostics.
- Playbook adaptations skip or reframe 11 of 20 playbooks.
- Hook adaptations reframe 8 of 16 hooks.
- Default output audience becomes
self. - Voice shifts to direct, personal address without team or board assumptions.
Solo mode persists across sessions. It is stored in memory, not in session state.
Syntax
/solo
Parameters
None.
Examples
> /solo
Solo mode activated.
You are the company. Every skill, diagnostic, playbook, and template now adapts
for a solopreneur context. Team-oriented diagnostics are rerouted. Board and
investor templates reframe as personal analysis. The system defaults to you as
the audience.
What changed:
Skills: 158 scored for solo relevance (47 critical, 56 high, 28 moderate, 27 low)
Templates: 48 available (30 reframed, 10 as-is, 8 unchanged)
Diagnostics: 20 available (12 as-is, 5 reframed, 3 skipped with reroutes)
Playbooks: 20 available (8 as-is, 8 reframed, 4 skipped with alternatives)
Hooks: 16 active (8 as-is, 8 reframed)
Mode persists across sessions. Use /solo off to deactivate.
> /solo
Solo mode is already active (since 2026-03-26). No change.
Use /solo status for details or /solo off to deactivate.
What Changes When Activated
| System Layer | Change |
|---|---|
| Memory (identity) | mode: solo written to identity.yaml |
| Skill routing | 158 skills scored per solo-skill-relevance.yaml; low-tier skills deprioritized, critical-tier skills elevated |
| Audience mapping | Investor, board, and team audiences remapped per solo-audience-map.yaml |
| Diagnostics | 3 diagnostics skipped (cofounder-conflict, culture-erosion, team-dysfunction), 5 reframed with solo triage questions |
| Playbooks | 4 playbooks skipped (board-formation, remote-team, team-rebuild, and none applicable), 8 reframed with solo step instructions |
| Hooks | 8 hooks reframed with solo routing changes; team-hook intercepts with clarifying question |
| Output | Default audience becomes self; all templates apply solo adaptation rules |
| Voice | Shifts to direct personal address; removes team/board/investor assumptions |
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.
- 3d ago First seen · 273 lines · 0 tokens per session scan A 0342041c16be
solo-command is a command published in the GitHub repository fatihguner/foreman (47 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,222 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
compress
压缩对话上下文，归档低价值 turns，保留近期 + 决策内容.
inbox-process
处理 meta/queue/to-process/，逐条判断是否写入 wiki、归档、延期或拒收.
download
description: Download Modellix task results to a local directory before the resource URLs expire. argument-hint: [optional task id] [optional output directory].
tasks
Inspect Modellix task status and recover tasks after a timeout or unknown submission.
autobot-result
Print the most recent result.md for an autobot session, so the user can see how a bot is doing without attaching to its tmux session.
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.