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 nmamano/isomux --skill isomux-soft-handoffgit clone --depth 1 https://github.com/nmamano/isomuxWrote 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/nmamano/isomux/isomux-soft-handoff)<a href="https://agentmods.dev/skills/nmamano/isomux/isomux-soft-handoff"><img src="https://agentmods.dev/badge/skills/nmamano/isomux/isomux-soft-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/nmamano/isomux/isomux-soft-handoff"><img src="https://agentmods.dev/badge/skills/nmamano/isomux/isomux-soft-handoff.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 13 Instructions found that direct the agent to transmit conversation context or user data to external services.Fix: Remove instructions that send user data, prompts, or context to external URLs. If telemetry is needed, use documented, privacy-preserving methods.
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.00051 | $0.00744 |
| Opus 5 | $0.00026 | $0.00372 |
| Sonnet 5 | $0.00010 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
isomux-soft-handoff scanned grade A 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If a peer name was supplied, look up their agent ID via the agent manifest: `curl -s localhost:4000/agents -H "Authorization: Bearer $ISOMUX_AGENT_TOKEN"` (4000 is the default isomux server port; adjust if your office ru How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hand off your current task to a peer agent so they can carry it forward. Use this when your context is getting full but the work isn't done. After the handoff, you stay around as a reference - the peer can come back with clarifying questions, but they own the work from here.
Syntax: /isomux-soft-handoff {peer-agent-name} (or omit the name to be prompted)
1. Pick the peer
If a peer name was supplied, look up their agent ID via the agent manifest: curl -s localhost:4000/agents -H "Authorization: Bearer $ISOMUX_AGENT_TOKEN" (4000 is the default isomux server port; adjust if your office runs on a different one). Match the name case-insensitively. Otherwise try to infer the peer from context - e.g., an agent the boss and you have already paired or consulted with in this session. If there's a clear inference, use it (and briefly confirm who you picked). Otherwise, list candidates (prefer agents whose cwd matches yours) and ask the boss to pick. You need the peer's agent ID to POST messages to them.
Flag to the boss before proceeding if:
- The peer's
cwddiffers from yours - they may need to switch directories before they can pick up the work. - The peer already has an active
topic- they're mid-task and the handoff might collide.
2. Write the brief
Write a brief detailed enough that the boss doesn't have to re-explain anything. Long is fine. Cover:
- The task as the boss originally framed it (quote them when possible).
- What's been done so far - specific file paths, commits, branches.
- What's left - the next concrete steps you'd be taking if you continued.
- Working state - dirty files, active worktrees, anything not in git yet.
- Decisions made along the way that aren't obvious from the diff.
- Open questions / unconfirmed assumptions so they know what to revisit with the boss.
- Pointers to context - relevant files, internal-docs pages, related skills. As a backstop, mention that the peer can read your session log via the
logDirfield in the agent manifest (theGET /agentscurl above) if they need deeper context.
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.
- 9d ago First seen · 44 lines · 51 tokens per session scan A 4c74634e937d
isomux-soft-handoff is a skill published in the GitHub repository nmamano/isomux (37 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 744 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
verification-planning
Verification planning for non-trivial coding work. Use before implementing a feature, bug fix, refactor, cross-system change, or high-confidence behavior change that needs a credible project-specific evidence path.