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 skills add cwinvestments/memstack --skill reportgit clone --depth 1 https://github.com/cwinvestments/memstackWrote 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/skills/cwinvestments/memstack/report)<a href="https://agentmods.dev/skills/cwinvestments/memstack/report"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/report/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/cwinvestments/memstack/report"><img src="https://agentmods.dev/badge/skills/cwinvestments/memstack/report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00067 | $0.03295 |
| Opus 5.5 | $0.00027 | $0.01318 |
| Sonnet 5.5 | $0.00013 | $0.00659 |
| Haiku 4.5 | $0.00007 | $0.00330 |
Grade A, and why
report 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report: Writing the Session Report
The session states what it did, in a file, once, at the end.
Activation
Output Report: writing the session report..., then follow the rules below.
Context Guard
| Context | Status | Priority |
|---|---|---|
| The prompt contains "Report per memstack:report" | ACTIVE, write the file before finishing | P1 |
| The prompt's first non-blank line starts with a configured trigger | ACTIVE, same requirement | P1 |
| The prompt matched a prefix trigger, but is under 40 characters | DORMANT, see the floor below | n/a |
| The prompt asks for a summary, a recap or a status line | DORMANT, answer in the terminal, no file | n/a |
| A long session ends and nobody asked for a report | DORMANT, an unrequested file is litter | n/a |
| The prompt asks for a diary or a handoff | DORMANT, that is Diary and Project, not this | n/a |
Triggers
The phrase always arms, on every install, with nothing configured. It is a phrase rather than a keyword because "report" appears in ordinary prose constantly.
Two environment variables add standing triggers on top of it. Both are unset by default, so a shipped install arms on the phrase and on nothing else.
| Variable | Effect |
|---|---|
MEMSTACK_REPORT_ON_TASK_PROMPTS |
Set to 1, arms any prompt whose first non-blank line starts with Working directory:. Any other value, including 0, changes nothing. |
MEMSTACK_REPORT_TRIGGERS |
Extra prefixes, semicolon separated, each matched against the first non-blank line. Surrounding spaces are trimmed, so Task briefing:; Ticket: configures two. |
Working directory: is separated out rather than left to the general list
because it is the opening line of a dispatched task prompt, which is the shape
this was built for, and because arming on it by default would file a report for
a large share of every prompt anyone writes.
When either variable is configured, the SessionStart hook injects one sentence saying so. That sentence is the only announcement: a prompt carrying the phrase announces the requirement itself, so a default install is told nothing and pays nothing.
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.
- 1mo ago Changed · +63 lines e4f0f32d1256
- 1mo ago First seen · 181 lines · 67 tokens per session scan A 9c141cfa81a4
report is a skill published in the GitHub repository cwinvestments/memstack (425 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 3,295 once invoked, about $0.0003 per session on Opus 5.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-09-06.
Other skills, from other repositories
catchup
Restore context after /clear by summarizing recent work and project state.
atomic-wiki
Conversational wiki and capture-bucket routing. Fires when the user wants a place, space, or folder for notes, research, tickets, raw dumps, or knowledge capture — checks the block in /.claude/CLAUDE.md; if the cwd is under a registered realm, creates the folder as a bucket via atomic wiki bucket add rather than a…
memory-factcheck
A check that compares the project’s saved agent notes with the current code, database, issue tracker, and files. It identifies notes whose claims are outdated or no longer match reality.
fable-context-thrift
Use at the start of any multi-step task and during exploration — before reading files, searching, or re-checking completed work, especially when tempted to read whole files, re-verify known facts, or run independent lookups one at a time.
context-mode
Use context-mode tools (ctxexecute, ctxexecutefile) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page…
deep-clean
Full-spectrum consolidation of AI agent configuration files. Goes beyond memory-only dream skills: audits and optimizes context files (AGENTS.md/AGENTS.md/GEMINI.md/.cursorrules), rules, skills, and memory. Detects stale references, dead file paths, duplicated rules, stack mismatches, contradictions, vague directives…