Borrowing it
Nothing to install: this file belongs to Undertone0809/rudder. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Undertone0809/rudder/main/.agents/skills/maintainer/delivery-lifecycle-maintainer/SKILL.mdgit clone --depth 1 https://github.com/Undertone0809/rudderWrote 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/undertone0809/rudder/delivery-lifecycle-maintainer)<a href="https://agentmods.dev/skills/undertone0809/rudder/delivery-lifecycle-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/delivery-lifecycle-maintainer/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/undertone0809/rudder/delivery-lifecycle-maintainer"><img src="https://agentmods.dev/badge/skills/undertone0809/rudder/delivery-lifecycle-maintainer.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.00058 | $0.02228 |
| Opus 5 | $0.00029 | $0.01114 |
| Sonnet 5 | $0.00012 | $0.00446 |
| Haiku 4.5 | $0.00006 | $0.00223 |
Grade A, and why
delivery-lifecycle-maintainer 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Delivery Lifecycle Maintainer
Own the root delivery state for one bounded Rudder task. The purpose is to make the final handoff truthful when implementation, acceptance, integration, or concurrent work changes the candidate. This is a thin coordinator and evidence ledger, not another implementation, review, verification, release, or general Git skill.
Scope and boundaries
Use this skill when a high-risk task under AGENTS.md section 9.1 needs a shared
ledger to keep source, runtime, acceptance, and integration evidence consistent:
intent -> implementation -> review -> black-box acceptance -> integration -> delivered ref
It is especially useful for concurrent shared main integration, multiple branches,
long-running agents, candidate replacement, budget/deadline changes, or a
handoff that needs exact source and receipt identity.
Crossing two routine stages or encountering unrelated dirty paths alone is not a trigger. Keep ordinary tasks in a concise change/check/Git handoff. Once a full packet is warranted, its required identities and validation remain mandatory.
- Preserve the user's raw request, later corrections, non-goals, and explicit authorization. Never replace the request with a convenient summary.
- Route implementation to the implementer, product judgment to
agent-work-reviewer-maintainer, black-box terminal observation toproduct-acceptance-verifier-maintainer, and public release/publish work torelease-maintainer. Record their receipts; do not impersonate them. - Do not decide Git conflict meaning, rewrite history, publish, or delete external state. When an explicitly authorized local integration is needed, record the Git operator's evidence and enforce the identity gates below.
- Do not create a worktree as ceremony. Start from the named checkout/main; isolate only after a real conflict, concurrent-write risk, destructive operation, or independent build/runtime requirement is observed.
- Reuse the user's existing authorization. A specialist handoff or new workflow stage is not another permission boundary. Recoverable failures and stale receipts require repair, not an automatic final blocked response.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today Changed · +1 lines e9ded166dfe1
- 2d ago Changed · +11 lines · -66 tokens per session 43e750a55e20
- 9d ago First seen · 193 lines · 124 tokens per session scan A 500dfb936c15
delivery-lifecycle-maintainer is a skill published in the GitHub repository Undertone0809/rudder (288 stars, last pushed today), licensed Apache-2.0. It adds 58 tokens to every session and 2,228 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.