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 hybridlabor-api/bdb-dev-optimized-agent-skills --skill agent-pipelinegit clone --depth 1 https://github.com/hybridlabor-api/bdb-dev-optimized-agent-skillsWrote 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/hybridlabor-api/bdb-dev-optimized-agent-skills/agent-pipeline)<a href="https://agentmods.dev/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/agent-pipeline"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/agent-pipeline/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/hybridlabor-api/bdb-dev-optimized-agent-skills/agent-pipeline"><img src="https://agentmods.dev/badge/skills/hybridlabor-api/bdb-dev-optimized-agent-skills/agent-pipeline.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.00065 | $0.01286 |
| Opus 5 | $0.00032 | $0.00643 |
| Sonnet 5 | $0.00013 | $0.00257 |
| Haiku 4.5 | $0.00006 | $0.00129 |
Grade A, and why
agent-pipeline 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 6d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔄 BDB Software Engineering Pipeline
When orchestrating or executing autonomous software development, follow the
lifecycle below — but the real, runnable implementation is
.agents/graph.md, invoked via /startcycle-graph
(see skills/basic/startcycle-graph/SKILL.md).
This file is a lifecycle summary, not a second spec — if it and graph.md
ever disagree, graph.md is right.
define plan build verify + review ship
┌──────┐ ┌──────┐ ┌────────────┐ ┌──────────────┐ ┌─────────┐
│ Goal │ ─▶ │ Plan │ ─▶ │ UI/UX, │ ─▶ │ Reviewer │ ─▶ │ Shipping│
│ │ │ │ │ Engineering,│ │ (adversarial)│ │ (gate) │
│ │ │ │ │ Media/Event│ │ │ │ │
└──────┘ └──────┘ └────────────┘ └──────────────┘ └─────────┘
Architect TechLead the build nodes no-progress guard requires GO
run in parallel repairs loop back to actually ship
There is no separate /spec, /plan, /build, /test, /review, or
/ship slash command — an earlier version of this file described those and
a Planner_Orchestrator agent that no longer exists (split into Architect +
TechLead; see graph.md's Nodes section for why). The whole lifecycle above
runs through the single /startcycle-graph entry point, which invokes each node
in turn per graph.md's edge table:
| Stage | Node(s) | Reads | Writes |
|---|---|---|---|
| Define + Plan | Architect, TechLead | state.goal |
state.artifacts.plan |
| Build | Godmode_UI_UX, Godmode_Engineering, Godmode_Media_EventTech (if needed) | the plan | their own artifacts |
| Verify + Review | Reviewer | build artifacts + contract only, never the implementer's claim | state.findings |
| Ship | Godmode_Shipping | all artifacts, findings | state.gate, requires a human GO |
The one rule, unchanged from graph.md: these nodes never invoke each
other. A dispatcher — the /startcycle-graph workflow, or the main session acting
as one — reads production_artifacts/state.json after each node returns and
decides what runs next.
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.
- 6d ago First seen · 90 lines · 65 tokens per session scan A dae9cde8c044
agent-pipeline is a skill published in the GitHub repository hybridlabor-api/bdb-dev-optimized-agent-skills (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,286 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-09-03.
Other skills, from other repositories
mcp-host-styling-integration
Integrates MCP App UI with host theming system. Applies host CSS variables, handles onhostcontextchanged, safe area insets, display mode detection, and fullscreen configuration.
context-engineering
Dynamic context injection, mode switching (dev/review/research), selective loading, and strategic compaction for token optimization.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
multi-app-orchestration
Orchestrate workflows across multiple applications and APIs — inter-app coordination, data handoff, and multi-system task completion.
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
bento
Modular grid layout with card-like blocks, clear hierarchy, soft spacing, and subtle visual contrast for organized, scannable interfaces.