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/hdk10/orgkit/org-statusgit clone --depth 1 https://github.com/hdk10/orgkitWhat 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.00040 | $0.00928 |
| Opus 5 | $0.00020 | $0.00464 |
| Sonnet 5 | $0.00008 | $0.00186 |
| Haiku 4.5 | $0.00004 | $0.00093 |
Grade A, and why
org-status 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Show me the current state of the org.
Steps
-
Regenerate ORG.md and ORG_PLAN.md to ensure they reflect the current filesystem:
python3 .org/sync_org.pyIf the script errors, report the error and continue with whatever ORG.md / ORG_PLAN.md exist on disk.
-
Read
.org/roles.json,ORG.md, andORG_PLAN.md(if present). -
For each role, collect:
- Role name and
descfrom roles.json. - Number of registered folders in
roles.<role>.folders. - Presence of
.last_promotemarker at<role>/memory/.last_promote— read it (JSON withtsandisokeys) and compute days since promotion. - Presence and non-emptiness of
<role>/memory/_pending.md— check if it contains any non-drained, non-comment lines (i.e., real pending content beyond a "Drained" marker line).
- Role name and
-
Check for drift by reading ORG.md for any "Unmapped" or "Missing" sections generated by sync_org.py. Collect them.
-
Render a status table using this format:
Org Status — <today's date> ═══════════════════════════════════════════════════════ ROLES ────────────────────────────────────────────────────── Role Folders Brain age Pending Action ────────────────────────────────────────────────────── <role> <N> <X>d ago YES/NO <tag> ... Action tags: STALE+PENDING → run /role-promote <role> (brain >7d old AND has pending content) STALE → consider /role-promote <role> (brain >7d old, no pending) PENDING → run /capture <role> then /role-promote <role> (pending, brain fresh) OK → nothing needed ────────────────────────────────────────────────────── DRIFT ────────────────────────────────────────────────────── Unmapped folders (on disk, not in any role): <list or "none"> Missing folders (in roles.json, not on disk): <list or "none"> ────────────────────────────────────────────────────── SUMMARY <N> roles | <M> STALE+PENDING | <K> STALE | <J> PENDING | <X> unmapped | <Y> missing -
If any roles are STALE+PENDING, list them explicitly at the bottom as a recommended action list:
Recommended actions: /role-promote <role> — <N> days stale, has pending content ... -
If
ORG_PLAN.mdexists, read it and display:- The progress bar line (e.g.
Progress: ███████░░░ 7/12 done) - Up to 3 next unchecked items with their hints, formatted as:
Adoption plan (ORG_PLAN.md): Progress: ███████░░░ 7/12 done Next up: [ ] <item text> → <hint>
If
ORG_PLAN.mddoes not exist, suggest runningpython3 .org/plan.pyto generate it. - The progress bar line (e.g.
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 · 81 lines · 40 tokens per session scan A 3bb874b95f06
org-status is a command published in the GitHub repository hdk10/orgkit (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 928 once invoked, about $0.0002 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 commands, from other repositories
update-changelog-and-tag
You are preparing a release. Follow these steps precisely.
plan-status
Render the current plan tree. Alias for /aura-frog:plan status (v3.7.2+).
help
Category: System Syntax: /help [command|topic].
_registry-protocol
This protocol is MANDATORY for ALL commands, agents, and phases.
mach12:issue-review
Read a GitHub issue and all comments, review the implementation plan, and present findings.
mach12:gh-pr-read
Read a GitHub pull request's title, body, and all top-level PR conversation comments; optionally locate an HTML-marker comment.