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 skills/collindjohnson/manas/setup-manasnpx skills add collindjohnson/manas --skill setup-manasgit clone --depth 1 https://github.com/collindjohnson/manasWhat 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.00063 | $0.00757 |
| Opus 5 | $0.00032 | $0.00378 |
| Sonnet 5 | $0.00013 | $0.00151 |
| Haiku 4.5 | $0.00006 | $0.00076 |
Grade A, and why
setup-manas 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Manas
Guide the user through Manas setup without choosing an archive or enabling a scheduler on their behalf.
Workflow
-
Confirm the
manascommand is available. For a verified release binary that is not yet installed, run itsinstallsubcommand. In a source checkout where it is not installed, replacemanasin every command below withbun run src/cli.ts. -
Inspect without mutation:
manas setup --detect-only --json -
Summarize detected providers, readable conversations, and warning/failure counts. Explain that the default archive is Manas-owned. If the user wants Obsidian, iCloud, or another location, collect an explicit archive path.
-
Ask the user to approve the archive location before writing configuration.
-
Generate a read-only preview using the approved location:
manas setup --preview --archive <approved-path> --jsonOmit
--archivewhen the user approves the Manas default. -
Report exact create, update, skip, warning, and failure totals. Do not continue if failures are nonzero.
-
Ask for explicit approval to perform the initial sync and enable the daily macOS scheduler. Offer configuration without scheduling when requested.
-
After approval, run one of:
manas setup --yes --archive <approved-path> --json manas setup --yes --archive <approved-path> --no-schedule --json -
Verify archive integrity and inspect scheduler status using the
configPathreturned by setup:manas verify --config <config-path> manas sync-status --config <config-path> -
Report the configured archive, detected providers, initial totals, scheduler state, last successful sync, and warnings.
-
For a broken installed scheduler, use the release binary's repair mode and require a fresh preview/approval. For an old chat-history-sync LaunchAgent, explain that it is retained by default; only run
manas setup --retire-legacy --yes --jsonafter the user explicitly approves its timestamped backup and unload.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 60 lines · 63 tokens per session scan A 862010791858
setup-manas is a skill published in the GitHub repository collindjohnson/manas (0 stars, last pushed 8d ago), licensed MIT. It adds 63 tokens to every session and 757 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
phase-orchestrator
Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes…
write-phase-plan
Writes or restructures an implementation plan in the format the phase-orchestrator skill consumes: dependency-ordered phases with explicit scope, acceptance criteria, validation commands, and status/log conventions. Use when the user asks to write a plan for phase orchestration, prepare a plan or PRD for delegated…
kb
Operate a hraness/kb local-first Markdown knowledge base for coding-agent memory. Use when a user asks to search or query a KB or Obsidian vault; load repository context, plans, decisions, concepts, backlinks, semantic search, or Git provenance; save, clip, scrape, or archive a URL, article, social thread, signed-in…
phase-final-reviewer
End-to-end reviewer for a completed multi-phase feature at the end of a phase-orchestrator run. Use after all requested phases are finalized: inspects the whole feature against the plan and PRD/spec, hunting integration bugs across phase boundaries, missing acceptance criteria, stale plan state, and validation gaps.…
phase-implementer
Implements exactly one phase of a multi-phase plan during a phase-orchestrator run. Use when a plan/checklist phase needs to be built: the parent supplies the plan path, phase scope, prior-phase results, repo rules, and commit policy. Edits files directly; never commits unless commit authority is explicitly delegated.…
phase-reviewer
Reviews and fixes a just-implemented phase of a multi-phase plan during a phase-orchestrator run. Use after a phase's implementation and initial validation: checks the phase against the plan, PRD/spec, repo conventions, security, tenancy/data ownership, migrations, and test coverage, and patches bounded low-risk…