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 DongDuong2001/pudo-code-system --skill pudo-handoffgit clone --depth 1 https://github.com/DongDuong2001/pudo-code-systemWrote 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/dongduong2001/pudo-code-system/pudo-handoff)<a href="https://agentmods.dev/skills/dongduong2001/pudo-code-system/pudo-handoff"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/pudo-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/dongduong2001/pudo-code-system/pudo-handoff"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/pudo-handoff.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.00234 |
| Opus 5.5 | $0.00024 | $0.00094 |
| Sonnet 5.5 | $0.00012 | $0.00047 |
| Haiku 4.5 | $0.00006 | $0.00023 |
Grade A, and why
pudo-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 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
PUDO Handoff
Collect facts from this session, not guesses: the task, the current PUDO phase, scope, files read, decisions, assumptions, tests run with results, remaining risks and the single next action.
- When the PUDO MCP server is connected, call
pudo.updateSessionHandoffwith those fields andconfirmWrite: true. - Otherwise write
.pudo/session.mdwith the headings Task, Current Phase, Scope, Files Inspected, Decisions Made, Assumptions, Tests Run, Remaining Risks, Next Action. - If
.pudo/auto-handoff.mdexists (written by the PreCompact hook), use it as a source, then check each fact before copying it.
The Next Action must be one concrete step someone can start without asking a question.
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 · 18 lines · 59 tokens per session scan A 703114d89381
pudo-handoff is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 234 once invoked, about $0.0002 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-10-24.
Other skills, from other repositories
triage
Apply a formal state machine to issues — assign category (bug/enhancement/question/spike) and state (needs-triage → needs-info → ready-for-agent → ready-for-human → wontfix). Issues marked ready-for-agent become inputs to supergraph:plan. Use when processing a backlog, reviewing new issues, or preparing work for…
project-flow-ops
Use when projects or tasks need explicit state, WIP control, ownership, definitions of done, blocker handling, and verified closure.
daily-briefing
Daily orientation and chief-of-staff briefing. Pulls from Slack (saved items), Gmail (important/starred), Google Calendar (today's events), Jira CLI (configured projects), and Todoist CLI, validates every action item, synthesizes a prioritized briefing using three consequence-based tiers, then produces a decisive…
jira
Manage Jira issues, sprints, and epics via CLI — jira-cli (ankitpokhrel/jira-cli) for bearer/basic-auth instances, acli (Atlassian's official CLI) for OAuth-only Jira Cloud tenants. Trigger on: jira, jira-cli, acli, ticket, issue key (e.g. PROJ-123), work item, epic, sprint, transition/move ticket, comment on ticket…
estimate
Produces time and complexity estimates for features, tasks, or sprints using story points, t-shirt sizing, or day estimates. Use when the user asks for an estimate, wants to size a feature, or mentions estimation or planning poker.
launch-checklist
Generates a comprehensive software launch checklist covering technical readiness, customer communications, support, and go-live steps. Use when preparing for a product launch or when the user mentions launch checklist or go-live readiness.