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/ferroxlabs/ijfw/memory-consentgit clone --depth 1 https://github.com/FerroxLabs/ijfwWhat 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.00023 | $0.00159 |
| Opus 5 | $0.00012 | $0.00079 |
| Sonnet 5 | $0.00005 | $0.00032 |
| Haiku 4.5 | $0.00002 | $0.00016 |
Grade A, and why
memory-consent 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 3d 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
Writes .ijfw/.automem-consent with {"consented": true|false, "at": "<iso>"}.
yes-- auto-memorize runs at session end, promotes feedback/signals to memory.no-- fully disabled. Session-end synthesizer exits silently.ask-- clears consent; auto-memorize will ask again next time it would fire.
Acknowledge with one line confirming the new state. Print the contents of .ijfw/.automem-consent so the user sees what was written.
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.
- 3d ago First seen · 13 lines · 23 tokens per session scan A 9c76fefb5ee0
memory-consent is a command published in the GitHub repository FerroxLabs/ijfw (210 stars, last pushed 9d ago), licensed MIT. It adds 23 tokens to every session and 159 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-30.
Other commands, from other repositories
constitution
根据交互输入或已提供原则创建或更新项目章程，并确保相关模板保持同步。.
taskstoissues
基于现有设计制品，将任务转换为可执行、带依赖顺序的 GitHub Issues。.
meta-theory
Run the MetaKim meta-theory governance dispatcher.
core-review
Review code changes against SpecOps project-specific patterns. Catches recurring failure modes from real PRs — tool abstraction violations, generated file drift, cross-platform gaps, variable inconsistencies, and more. Complements full-review-gate (generic quality) and pr-fix (applying bot comments).
full-review-gate
Perform a comprehensive repository code review in an isolated worktree. Fix P0/P1 findings and ship them as a PR targeting the current branch.
ship-pr
Commit all changes to a new branch, push, and open a PR for review. The original branch stays clean.