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/kernalix7/aips/aips-statusgit clone --depth 1 https://github.com/kernalix7/AIPSWhat 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.00020 | $0.00636 |
| Opus 5 | $0.00010 | $0.00318 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
aips-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 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
/aips:status
Show the AIPS state of the current project. Read-only — pure file reads, no analysis.
What it does
- AIPS version — read
~/.claude/plugins/AIPS/.claude-plugin/plugin.json.version. Print. - Init date —
stat -c %y .priv-storage/CLAUDE.md(or BSDstat -f %SBon macOS). Print asinit date: YYYY-MM-DD. - Last update —
statmtime on.priv-storage/CLAUDE.mdAND most-recent template in~/.claude/plugins/AIPS/templates/; report the more recent. Print aslast update: YYYY-MM-DD. - CLAUDE.md sections present —
grep -E '^## [0-9]+\.' .priv-storage/CLAUDE.md→ list section numbers found (expect 1-7 + 11). - Memory — count files in
.priv-storage/memory/*.md, total size, list category names. - Sessions — for each of
current.md,recovery.md, latesthandoff-*.md: print filename + age (e.g.current.md: 3m ago,handoff-2026-05-18.md: 1d ago). - Dep plugins active — for each of
agentmemory,caveman,rtk,codex-plugin-cc: reportinstalled/missingbased on presence under~/.claude/plugins/. - Root symlinks — confirm
CLAUDE.md,AGENTS.md,.cursorrules,.vscode/settings.jsonresolve into.priv-storage/.
Output
[status] AIPS version v6.0.0
[status] init date 2026-05-12
[status] last update 2026-05-19
[status] CLAUDE.md sections 1, 2, 3, 4, 5, 6, 7, 11
[status] memory files 6 files, 12 KB (project_versioning, reference_install_url, ...)
[status] current.md 3m ago
[status] recovery.md 2h ago
[status] latest handoff handoff-2026-05-18.md (1d ago)
[status] dep plugins agentmemory: installed, caveman: installed, rtk: installed, codex-plugin-cc: missing
[status] root symlinks 4/4 valid
Rules
- Read-only. Never write or edit.
- Never analyze content — just report what's present.
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 · 40 lines · 20 tokens per session scan A 5352192e446f
aips-status is a command published in the GitHub repository kernalix7/AIPS (5 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 636 once invoked, about $0.0001 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.