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-scopegit 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.00012 | $0.00733 |
| Opus 5 | $0.00006 | $0.00367 |
| Sonnet 5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade B, and why
aips-scope scanned grade B with 1 finding 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
SCOPE_SH="$(find ~/.claude/plugins/cache/AIPS/AIPS/lib -name scope.sh 2>/dev/null | head -1)" How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/aips:scope
Print a per-file scope table showing what lives globally (shared across all projects), what is globalized for this project (keyed by path), and what stays per-project (committed or in .priv-storage/). Flags legacy v6.0 artifacts that should be migrated via /aips:upgrade --to v7.0.
Args
/aips:scope $ARGUMENTS
$ARGUMENTS = optional <project_root> (default: pwd).
What it does
SCOPE_SH="$(find ~/.claude/plugins/cache/AIPS/AIPS/lib -name scope.sh 2>/dev/null | head -1)"
[ -z "$SCOPE_SH" ] && SCOPE_SH="$(find ~/.claude/plugins -name scope.sh 2>/dev/null | head -1)"
bash "$SCOPE_SH" "${ARGUMENTS:-$(pwd)}"
The script emits a 4-column table:
FILE/DIR SCOPE SIZE MTIME
Grouped into the sections below.
Sections
-
Global (shared, version-controlled by the plugin)
~/.claude/plugins/cache/AIPS/~/.claude/hooks/~/.claude/agents/~/.claude/commands/~/.claude/skills/~/.claude/output-styles/~/.claude/statusline~/.local/bin/aips-*
-
Globalized state for this project (path-keyed)
~/.claude/sessions/<path-hash>/~/.claude/projects/<path-encoded>/memory/
-
Per-project (lives in repo or
.priv-storage/).priv-storage/CLAUDE.md.priv-storage/WORK_STATUS.md.priv-storage/.mcp.json.priv-storage/.claude/agents/tech-lead.mdand*-team.mdtmp-igbkp/backup output
-
Legacy v6.0 — should be globalized via
/aips:upgrade --to v7.0(warning lines, prefixed[legacy]).priv-storage/.claude/{hooks,skills,output-styles,statusline}- Per-project AIPS block in
.gitignore .priv-storage/memory/*(when no global mirror exists).priv-storage/sessions/*(when no global mirror exists)
Summary
AIPS version: 7.0 (from .priv-storage/.aips-version)
path hash: ab12cd34ef56
path encoded: -home-user-projects-myapp
scope split: globalized 70% per-project 30% legacy 0%
total tracked files: N
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 · 78 lines · 12 tokens per session scan B 26de20e0d555
aips-scope is a command published in the GitHub repository kernalix7/AIPS (5 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 733 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). 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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.