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 skills/dzhng/duet-agent/releasenpx skills add dzhng/duet-agent --skill releasegit clone --depth 1 https://github.com/dzhng/duet-agentWrote 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/dzhng/duet-agent/release)<a href="https://agentmods.dev/skills/dzhng/duet-agent/release"><img src="https://agentmods.dev/badge/skills/dzhng/duet-agent/release.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.00065 | $0.00396 |
| Opus 5 | $0.00032 | $0.00198 |
| Sonnet 5 | $0.00013 | $0.00079 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
release 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
Release
Use this workflow to publish a new @duetso/agent version through the GitHub release workflow.
Steps
-
Confirm the working tree and branch:
- Run
git status --short --branch. - If there are unrelated changes, ask before including them.
- Release from
mainunless the user explicitly says otherwise.
- Run
-
Choose the next version:
- Read
package.json. - Increment the patch version by default.
- Use the tag name
v<version>, for examplev0.1.12. - Check that the tag does not already exist locally or remotely.
- Read
-
Update release metadata:
- Change only
package.jsonfor a normal version bump. - Do not edit
bun.lockunless the package manager updates it as part of a dependency change.
- Change only
-
Verify before committing:
- Run
bun run check-types. - Run
bun run lint. - Run broader tests only when the release includes code changes or the user asks for them.
- Run
-
Commit:
- Stage
package.json. - Commit with
chore: release v<version>.
- Stage
-
Tag and push:
- Create an annotated tag:
git tag -a v<version> -m "v<version>". - Push
main:git push origin main. - Push the tag:
git push origin v<version>.
- Create an annotated tag:
-
Report back:
- Include the new version, commit SHA, tag name, pushed refs, and verification commands.
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 · 43 lines · 65 tokens per session scan A e14380ced4a9
release is a skill published in the GitHub repository dzhng/duet-agent (42 stars, last pushed yesterday), licensed Apache-2.0. It adds 65 tokens to every session and 396 once invoked, about $0.0003 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 skills, from other repositories
harness-creator
Build, audit, and improve harnesses that make AI coding agents reliable: AGENTS.md/CLAUDE.md instruction files, feature/state tracking, verification gates, scope boundaries, session handoff, memory persistence, context budgets, tool-permission safety, and multi-agent coordination. Use this whenever a coding agent is…
evaluator-write-qa
Internal Auto-Harness evaluator skill for sprint QA and QA report writing. Use only inside the Evaluator subagent during qa mode.
evaluator-review-contract-parallel
Internal Auto-Harness evaluator skill for parallel sprint contract review before implementation. Use only inside the Evaluator subagent during review mode.
evaluator-write-final-parallel
Internal Auto-Harness evaluator skill for parallel final QA report aggregation. Use only inside the Evaluator subagent during evaluatorfinalparallel.
evaluator-write-qa-parallel
Internal Auto-Harness evaluator skill for parallel sprint QA and QA report writing. Use only inside the Evaluator subagent during evaluatorqaparallel.
evaluator-write-retest-parallel
Internal Auto-Harness evaluator skill for parallel sprint retest and retest report writing. Use only inside the Evaluator subagent during evaluatorretestparallel.