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 drivestream-lab/prayog-skills --skill create-board-ticketsgit clone --depth 1 https://github.com/drivestream-lab/prayog-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/drivestream-lab/prayog-skills/create-board-tickets)<a href="https://agentmods.dev/skills/drivestream-lab/prayog-skills/create-board-tickets"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/create-board-tickets/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/drivestream-lab/prayog-skills/create-board-tickets"><img src="https://agentmods.dev/badge/skills/drivestream-lab/prayog-skills/create-board-tickets.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.00080 | $0.01476 |
| Opus 5 | $0.00040 | $0.00738 |
| Sonnet 5 | $0.00016 | $0.00295 |
| Haiku 4.5 | $0.00008 | $0.00148 |
Grade A, and why
create-board-tickets 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 11d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create board tickets
Human-walker equivalent of Gateflow board create
(forge.action: create_board_tickets).
One command after merge: read plan §9 → preflight → confirm → create.
There is no separate /board-seed content skill. At seed time WorkManifest
lives in the implementation plan §9 (walk-time carrier). After successful
seed, board issues are the long-term WorkManifest home — the plan file may
be purged at initiative closure
(prayog-skills/references/artifact-write-contract.md,
prayog-skills/references/workmanifest-contract.md).
Do not run before spec merge. Do not write product code.
NON-NEGOTIABLE
- Resolve layout from
.harness/profile.yamlor references/layout-defaults.md. - Spec merge gate first — merged
Implementation-Plan-{initiative}.mdon integration branch; closed spec PR hadspec-lgtmon merge head when verifiable. - Board binding — resolve programme board from read-only meta governance:
{workspace}/{meta_repo}/config/governance-*.yaml→project_board.name. If missing, runlaunchpad board-bind --client <id>and stop. Governance wins over plan §9target.projectfree text. - Validate WorkManifest before mutate — parse §9 YAML and run
scripts/workmanifest_contract.py/validate_workmanifestforapiVersion: prayog/v1+kind: WorkManifest. Requireworkmanifest-contract-pass(plan P16). Reject unsupportedapiVersion/kind. Do not create issues on a failing contract. Requireepic,work[]with wave idsW0…Wn, and each wave'stasks[]with stableTASK-*,implements,depends_on, exit proof, and verification as defined inprayog-skills/references/workmanifest-contract.md. - Projection only — project epic/wave/task summaries from the
canonical WorkManifest into board issue titles/bodies. After seed, board
holds long-term identity; do not invent TASK ids, REQ mappings,
dependencies, exit criteria, or proof summaries that are absent from §9
at seed time. Record created issue URLs/ids in the seed summary so
/pre-implementcan spend without requiring the plan file forever. - Idempotent — search existing issues by initiative label; create only missing items; link existing waves under EPIC when parent missing.
- Hierarchy — EPIC first, then each wave as sub-issue on the same org Project. Initiative label on every issue. Wave bodies retain TASK ids, REQ mappings, dependencies, exit criteria, and proof summary from the manifest.
- Explicit authorization before mutate. Present the seed plan; create only after the human confirms. Authorization, branch, commit, PR, label, and issue-creation behavior otherwise unchanged.
- Never apply approval labels (
*-lgtm). Tool-neutral Forge tooling (gh, project APIs, …) — examples only. - If tooling unavailable, print exact commands from
references/output-template.md and stop —
do not claim
seeded. - Ids:
prayog-skills/references/id-conventions.md. Paths:prayog-skills/references/artifact-write-contract.md. Checks: B1–B8.
What ships with it
7 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.
- 11d ago First seen · 115 lines · 80 tokens per session scan A 01fc0d4e3bc2
create-board-tickets is a skill published in the GitHub repository drivestream-lab/prayog-skills (2 stars, last pushed 4d ago), licensed MIT. It adds 80 tokens to every session and 1,476 once invoked, about $0.0004 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.