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 FerroxLabs/ijfw --skill ijfw-handoffgit clone --depth 1 https://github.com/FerroxLabs/ijfwWrote 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/ferroxlabs/ijfw/ijfw-handoff)<a href="https://agentmods.dev/skills/ferroxlabs/ijfw/ijfw-handoff"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-handoff/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/ferroxlabs/ijfw/ijfw-handoff"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ijfw/ijfw-handoff.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.00023 | $0.00257 |
| Opus 5.5 | $0.00009 | $0.00103 |
| Sonnet 5.5 | $0.00005 | $0.00051 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
ijfw-handoff 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.
What it actually says
Generate a structured handoff for session continuity.
Creating a Handoff
Capture in .ijfw/memory/handoff.md:
Handoff: <timestamp>
====================
Status
------
| Phase N | Wave NA | Step N.M | <done/in-progress/blocked> |
<What's done. What's in progress. What percentage complete.>
Decisions
---------
<Key decisions made this session with rationale. 1 line each.>
Modified Files
--------------
<Files created/edited with brief description of changes.>
Next Steps
----------
<Ordered list. What to do first when resuming.>
Blockers
--------
<Open questions, missing info, external dependencies.>
Rules:
- Max 30 lines. This loads at next SessionStart -- keep it lean.
- Specific file paths, function names, line numbers.
- Present tense for current state, imperative for next steps.
- No filler. Every line must help the next session start faster.
Loading a Handoff
Read .ijfw/memory/handoff.md. Display a 2-3 line summary. Set context for continuation.
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 First seen · 49 lines · 23 tokens per session scan A fe2aced6c5c3
ijfw-handoff is a skill published in the GitHub repository FerroxLabs/ijfw (214 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 257 once invoked, about $0.0001 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-05.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-reasoning
Use when a technical decision, trade-off, rejected alternative, architecture rationale, or design risk should be recorded or recovered.