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 YoungLeadersDotTech/young-leaders-tech-marketplace --skill diy-build-companiongit clone --depth 1 https://github.com/YoungLeadersDotTech/young-leaders-tech-marketplaceWrote 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/youngleadersdottech/young-leaders-tech-marketplace/diy-build-companion)<a href="https://agentmods.dev/skills/youngleadersdottech/young-leaders-tech-marketplace/diy-build-companion"><img src="https://agentmods.dev/badge/skills/youngleadersdottech/young-leaders-tech-marketplace/diy-build-companion/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/youngleadersdottech/young-leaders-tech-marketplace/diy-build-companion"><img src="https://agentmods.dev/badge/skills/youngleadersdottech/young-leaders-tech-marketplace/diy-build-companion.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.00061 | $0.02957 |
| Opus 5 | $0.00030 | $0.01478 |
| Sonnet 5 | $0.00012 | $0.00591 |
| Haiku 4.5 | $0.00006 | $0.00296 |
Grade A, and why
diy-build-companion 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DIY Build Companion
A single companion for planning and running DIY builds. It follows an assembly-line workflow with energy-aware work blocks and enforced breaks, and keeps the same project state in sync across Claude desktop, web, and the mobile app. This replaces the older five-skill Claude Code suite (diy-start, diy-resume, diy-progress, diy-break, diy-safety-check) with one skill and five modes.
Before you start (two things worth knowing). First, if you previously installed the older five skills (diy-start, diy-resume, diy-progress, diy-break, diy-safety-check), remove them so a request does not trigger both the old and new behaviour. Second, this skill keeps state in Google Drive, and reading it back is what fixes the cross-surface drift. Reading is reliable; writing may need your help in sessions without a Drive write tool, in which case the skill hands you the updated file to save rather than writing it silently (see the write rule below). On those sessions, expect to paste state back occasionally; it is the honest cost of never trusting a write that did not happen.
The one rule that fixes the cross-surface problem
The previous suite kept project state in a local file tree, so mobile and web each had their own copy and they drifted. Here, the single source of truth is a project folder in Google Drive, reached through the Google Drive connector that is available in the chat regardless of which device you are on. Every mode reads the current state from Drive before doing anything. Do not cache state in your head across turns or assume a local file is current: read Drive first.
Reads and writes are not symmetric, and this matters. The Drive connector reliably supports reading (search and fetch), so always pull the live state at the start of a turn. Writing back to Drive may not be available as a direct tool in every session. Before claiming any write, confirm a Drive write/update tool is actually present. If it is, use it and confirm the path. If it is not, do the honest fallback: produce the updated file as a fenced Markdown block and tell the user the exact filename and folder to save or replace it with. Never claim a write to Drive that did not happen - this was the original failure mode and silent false-writes are worse than an honest handback. When in doubt, hand back the block.
What ships with it
2 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 · 226 lines · 61 tokens per session scan A e4c5ddd0b39c
diy-build-companion is a skill published in the GitHub repository YoungLeadersDotTech/young-leaders-tech-marketplace (10 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 2,957 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
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.