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 agents/claude-genasis/genasis/pmgit clone --depth 1 https://github.com/claude-genasis/genasisWhat 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.00008 | $0.00114 |
| Opus 5 | $0.00004 | $0.00057 |
| Sonnet 5 | $0.00002 | $0.00023 |
| Haiku 4.5 | $0.00001 | $0.00011 |
Grade A, and why
pm 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.
What it actually says
pm overlay
project: blank-fixture
pm
Default base body for the pm role. The marker fence below this
line is owned by Genasis (attach/upgrade rewrites it). Anything
outside the fence is yours to edit.
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 · 17 lines · 8 tokens per session scan A 2b68d2fa9278
pm is an agent published in the GitHub repository claude-genasis/genasis (7 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 114 once invoked, about $0.0000 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 agents, from other repositories
chief-of-staff
Use this agent for morning briefing coordination, department status collection, and daily ops reporting. Deploy when: (1) Morning routine triggered - collects status from all departments, (2) MCP health monitoring needed - runs infrastructure health checks, (3) Department-level status summaries requested, (4) Critical…
scrum-leader
Use this agent for sprint planning, backlog grooming, velocity tracking, and agile coaching. Deploy when: (1) Sprint boundaries reached (day 1, 7, 14 of 2-week cycle), (2) Backlog grooming needed or estimation sessions required, (3) Daily standup aggregation and impediment tracking, (4) Velocity drift detected (>15%…
example-org-coordinator
Single entry point for the example-org engagement — board grooming on the example-board GitHub Project, status-report prep for the example-team mandant, and routing per rules/org/example-routing.md. Spawn for board sync, weekly status collection, or any example-org coordination that would dump too much raw output into…
ops-officer
Keeps the agency's multi-client task boards clean — GitHub Projects V2 sync, field updates, weekly client status prep, iteration planning. Spawn for board grooming or status-report collection across BigCorp, StartupXYZ, and internal work.
org-governance
Version: 1.0 Purpose: Define organizational hierarchy, tool access by role level, and enforcement rules.
github-issue-triage
How to run issue triage sweeps, manage issue dependencies, and apply triage labels. Spec-alignment auditing that may create issues lives in Specification & ADR discipline.