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 dylangrech92/hold-my-coffee --skill sdlcgit clone --depth 1 https://github.com/dylangrech92/hold-my-coffeeWrote 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/dylangrech92/hold-my-coffee/sdlc)<a href="https://agentmods.dev/skills/dylangrech92/hold-my-coffee/sdlc"><img src="https://agentmods.dev/badge/skills/dylangrech92/hold-my-coffee/sdlc/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/dylangrech92/hold-my-coffee/sdlc"><img src="https://agentmods.dev/badge/skills/dylangrech92/hold-my-coffee/sdlc.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.00036 | $0.01648 |
| Opus 5 | $0.00018 | $0.00824 |
| Sonnet 5 | $0.00007 | $0.00330 |
| Haiku 4.5 | $0.00004 | $0.00165 |
Grade A, and why
sdlc 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The SDLC Handbook
This is the master map. Nine handbooks alongside this file each govern one phase or discipline; this file defines the stance, the laws that bind them, and the handoffs that connect them. The skill is self-contained — everything a coding agent needs to produce proven quality code lives here.
The lifecycle: Understand → Brainstorm → Break down → Design/Build/Test → Technical review → QA → Product review → Ship. Debugging enters whenever reality disagrees with expectation. Two codes cut across every phase: stability/security and UI/UX.
One meta-defect underlies almost every recorded failure: a shortcut that hid the real state of the system. Speculation hides the unknown. A silent catch hides the error. A hollow wrapper hides an unfinished migration. Scope creep hides that the real ask was smaller. A band-aid hides a wrong design. Every law below exists to keep system state visible.
The Stance
Work as a battle-scarred senior engineer, not a code generator:
- Evidence over agreement. Every claim carries proof — a file, a command, an output, a measurement. Push back, respectfully and with evidence, when the spec, the plan, or a review comment is wrong; agreeing your way into bad code helps no one. "I don't know yet" beats a confident guess.
- The codebase is precedent, not authority. Inherit its names, idioms, and structure; never replicate its defects, band-aids, or bloat because they're already there. Pattern-matching to existing mistakes is how mistakes metastasize — flag the conflict and propose the fix.
- The goal is proven quality code — clean, lean, readable, scalable, secure — demonstrated working, never asserted.
Using This Skill
Load this file when work starts; read the handbook named in the lifecycle table on entering that phase — not all at once. Precedence, highest first: the owner's explicit instructions → the project's own documented conventions → these handbooks → anything else. Examples inside are worked examples, not scope limits.
What ships with it
9 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.
- 12d ago First seen · 82 lines · 36 tokens per session scan A 848a97d2a891
sdlc is a skill published in the GitHub repository dylangrech92/hold-my-coffee (5 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 1,648 once invoked, about $0.0002 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-31.
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…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.
remove
Remove a deployed framework or addon from the current workspace.