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.
git clone --depth 1 https://github.com/agentii-ai/growth-hacking-kitWrote 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/commands/agentii-ai/growth-hacking-kit/blogkit.taskstoissues)<a href="https://agentmods.dev/commands/agentii-ai/growth-hacking-kit/blogkit.taskstoissues"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/blogkit.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/commands/agentii-ai/growth-hacking-kit/blogkit.taskstoissues"><img src="https://agentmods.dev/badge/commands/agentii-ai/growth-hacking-kit/blogkit.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.00011 | $0.00412 |
| Opus 5.5 | $0.00004 | $0.00165 |
| Sonnet 5.5 | $0.00002 | $0.00082 |
| Haiku 4.5 | $0.00001 | $0.00041 |
Grade A, and why
blogkit.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.
This is a copy
100% identical to blogkit.taskstoissues — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Outline
Convert tasks.md into actionable GitHub issues maintaining structure and dependencies:
-
Load tasks.md: Parse sprints, phases, dependencies, and task details
-
Create GitHub Issues for Each Task:
- Issue title:
[SPRINT] [PHASE] Task description - Issue body: Full task description with acceptance criteria
- Labels: Sprint-based (sprint-0, sprint-1, etc.) + Phase-based (research, draft, review, copyedit, publish, measure)
- Milestone: Set per content sprint (Sprint 0, Sprint 1, etc.)
- Issue title:
-
Link Dependencies:
- Identify sequential tasks and create "blocks" relationships
- Add comments linking related tasks
- Document parallel execution opportunities with labels
-
Assign Roles:
- Add assignee based on task type:
- Research/Outline tasks → Writer
- Draft tasks → Writer
- Technical Review → SME
- Copyedit/SEO → Copyeditor
- Publish/Distribute → Marketing
- Measurement → Analytics/Owner
- Add assignee based on task type:
-
Add Acceptance Criteria:
- Each issue includes checkbox list for task completion
- Clear "Definition of Done" for each task type
-
Create Epic Issues:
- One epic per sprint (Sprint 0 Epic, Sprint 1 Epic, etc.)
- Link all sprint tasks as child issues
- Track sprint progress at epic level
-
Generate Summary:
- Show issue count by sprint and phase
- Display GitHub project/milestone links
- Provide workflow for team to track progress
NOTE: GitHub issues enable team collaboration and progress tracking.
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 · 51 lines · 11 tokens per session scan A 9668d90ee155
blogkit.taskstoissues is a command published in the GitHub repository agentii-ai/growth-hacking-kit (5 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 412 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to blogkit.taskstoissues, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
friday
End-of-week close-out. Reviews performance, digests team progress, cleans up project management, and saves session state.
team
Routes to team-manager skill for managing team members and credentials.
saleskit.checklist
Generate a custom checklist for the current feature based on user requirements.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
template
Manage issue templates for streamlined issue creation.