Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add postindustria-tech/agentic-toolkit/plugin install dev-practicesWrote 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/postindustria-tech/agentic-toolkit/execute)<a href="https://agentmods.dev/skills/postindustria-tech/agentic-toolkit/execute"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/execute/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/postindustria-tech/agentic-toolkit/execute"><img src="https://agentmods.dev/badge/skills/postindustria-tech/agentic-toolkit/execute.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.00114 | $0.03832 |
| Opus 5.5 | $0.00046 | $0.01533 |
| Sonnet 5.5 | $0.00023 | $0.00766 |
| Haiku 4.5 | $0.00011 | $0.00383 |
Grade A, and why
execute 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 1mo 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Execution (Molecular)
Molecular workflow for executing beads tasks. Creates an atom graph where each step is independently executable and survives context compaction. Research findings are stored in the bead itself, making each task self-contained.
Args
/dev-practices-execute <task-id-1> [task-id-2] [task-id-3] ...
One or more beads task IDs. Each task gets atoms chained in sequence. Multiple tasks execute sequentially.
Formula Selection
Auto-select based on task type -- run bd show <id> to check the type and
description:
| Task Type | Formula | Atoms per task | When to use |
|---|---|---|---|
bug |
bug-triage.yaml |
7 | Bugs that need reproduction and root cause analysis |
| Complex tasks | task-execute.yaml |
7 | Tasks needing research, architect review, or TDD (new features, refactors with unknowns) |
| Well-defined tasks | task-single.yaml |
3 | Tasks with clear descriptions, known code paths, no design decisions (test rewrites, allowlist fixes, mechanical changes) |
How to choose between task-execute and task-single:
- Does the task need research (unfamiliar code, unknown APIs)? ->
task-execute - Does the task need architect review (multiple valid approaches)? ->
task-execute - Does the task need TDD red-green (new production code)? ->
task-execute - Is the task self-contained (description says exactly what to do)? ->
task-single - Is the task test-only (rewriting tests, not production code)? ->
task-single - Is the task mechanical (remove from allowlist, update imports)? ->
task-single
Test-first is enforced in task-execute and bug-triage:
- Bugs: The
reproduceatom requires a failing test before thefixatom proceeds - Tasks (task-execute): The
write-testatom requires a failing regression test beforeimplementproceeds - Refactors:
write-testguards existing behavior with edge case tests before changes begin
task-single skips TDD because the work IS the test -- there's no separate production code to gate on. The execute atom runs the project quality command as the gate.
What ships with it
11 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.
- formulas/bdd-step.yaml 5.5 KB
- formulas/bug-triage.yaml 14 KB
- formulas/entity-remediate.yaml 4.9 KB
- formulas/integration-from-stub.yaml 5.6 KB
- formulas/migration-audit.yaml 3.2 KB
- formulas/obligation-test.yaml 4.0 KB
- formulas/structural-guard.yaml 4.4 KB
- formulas/task-execute.yaml 24 KB
- formulas/task-fix.yaml 13 KB
- formulas/task-single.yaml 6.8 KB
- scripts/cook_formula.py 12 KB runs code
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.
- 1mo ago First seen · 325 lines · 114 tokens per session scan A 38f8329e3a41
execute is a skill published in the GitHub repository postindustria-tech/agentic-toolkit (2 stars, last pushed 11d ago), licensed MIT. It adds 114 tokens to every session and 3,832 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
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.
ring:mapping-feature-relationships
Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…