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 wedabro/bro-skills --skill speckit.taskstoissuesgit clone --depth 1 https://github.com/wedabro/bro-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/wedabro/bro-skills/speckit.taskstoissues)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.taskstoissues"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.taskstoissues/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/wedabro/bro-skills/speckit.taskstoissues"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.taskstoissues.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.00026 | $0.00295 |
| Opus 5.5 | $0.00010 | $0.00118 |
| Sonnet 5.5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
speckit.taskstoissues 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.
What it actually says
Mission
Create an idempotent export that preserves task traceability, dependencies, acceptance checks, and phase grouping.
Inputs and Outputs
- Read
spec.md,plan.md,tasks.md, and repository issue conventions. - Write
.agents/memory/issues-export.mdplus a summary of skipped/malformed tasks; never create remote issues.
Protocol
- Validate task IDs, titles, user-story links, paths, dependencies, priorities, and acceptance text. Report duplicates and malformed rows.
- Generate one stable issue block per task with deterministic title, labels, phase/milestone, body, dependency links, acceptance checks, and source task ID.
- Preserve ordering and IDs across reruns; escape markdown safely and avoid secrets or environment-specific URLs.
- Group by phase and identify dependency cycles, orphan tasks, blocked tasks, and tasks lacking acceptance evidence.
- Report export counts, skipped items, and import instructions. A remote sync requires separate explicit authorization and provider configuration.
Completion Gate
Every valid task maps exactly once to an issue block, source links are retained, and malformed/unsafe items are visible rather than silently dropped.
Guard Rails
Read-only with respect to remote trackers. Do not create, update, close, or delete remote issues from this skill.
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 Changed · -7 lines · +6 tokens per session 2d8d16f84394
- 2mo ago First seen · 31 lines · 20 tokens per session scan A 6ff1742b2fcf
speckit.taskstoissues is a skill published in the GitHub repository wedabro/bro-skills (3 stars, last pushed 17d ago), licensed MIT. It adds 26 tokens to every session and 295 once invoked, about $0.0001 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
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
working-days-get-working-days
Calculate the number of working days between two dates, optionally accounting for country-specific holidays.
pm-karpathy-thinking
Stress-test a product decision, PRD, roadmap, experiment, or feature proposal using explicit assumptions, simplicity-first scope, surgical changes, and measurable verification loops. Use when product work is ambiguous, over-scoped, solution-led, risky, or needs a clear go/no-go recommendation.
glab-iteration
A GitLab command for managing project iterations, which are time-boxed work periods such as sprints.
pm-vietnamese
Create decision-ready, delivery-ready bilingual Vietnamese-English product management artifacts. Use for discovery, PRDs, user stories, prioritization, roadmaps, OKRs, metrics, experiment plans, feedback analysis, meeting synthesis, stakeholder updates, and pre-mortems.