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/albertomarturelo/sii/session-closegit clone --depth 1 https://github.com/albertomarturelo/siiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/albertomarturelo/sii/session-close)<a href="https://agentmods.dev/commands/albertomarturelo/sii/session-close"><img src="https://agentmods.dev/badge/commands/albertomarturelo/sii/session-close.svg" alt="Measured on agentmods" height="20"></a>What 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.00000 | $0.00270 |
| Opus 5 | $0.00000 | $0.00135 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
session-close 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 4d 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
Before this session ends, do ALL of the following. Do not skip any step.
-
Update
docs/CURRENT_STATUS.md:- Move completed items from "In Progress" to "Recently Completed".
- Add new items uncovered this session.
- Update "Known Issues" / "Open Decisions" if anything new surfaced.
- Re-rank "Next Priorities".
- Update the "Last updated" date to today.
-
If a convention was clarified or a pattern was corrected this session, update
docs/CONVENTIONS.mdaccordingly. Do NOT leave corrections only in chat history — they'll be lost next session. -
If a significant decision was made informally (in chat, in a review, in passing), propose creating an ADR via
/decision:newbefore closing. -
Stage all
docs/changes in the SAME commit/PR as the session's code changes. Context updates ship with code, not after.
Do NOT close the session without completing step 1.
After completion, output a one-paragraph session summary suitable for pasting into the PR description.
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.
- 4d ago First seen · 29 lines · 0 tokens per session scan A 07bf767f7ff7
session-close is a command published in the GitHub repository albertomarturelo/sii (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 270 tokens. 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
onplana-connect
Connect Claude Code to the Onplana MCP server, then verify it works.
broadcast
Post a message to the project inbox so other sessions on this project can see it. Supports targeting and priority.
presence
Show other claude-presence sessions and resource locks active on this project.
staff-event
Build a complete event staffing plan (configured-market match, W-2 rates, tier-based lead time, compliance) and prepare a buyer-submitted quote form.
whatneedsdoing
One honest "what needs doing" across the two work substrates — repo dev work (docs/backlog/ + open gripes + open GitHub PRs + Dependabot alerts) and the prod factory queue (open/doable todos) — plus a repo-hygiene scan (migration-number collisions · backlog lint · memory-index lint), a prod system-health read…
/spectra-archive
Archive a completed change.