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/croffasia/cc-blueprint-toolkitWrote 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/croffasia/cc-blueprint-toolkit/execute-task)<a href="https://agentmods.dev/commands/croffasia/cc-blueprint-toolkit/execute-task"><img src="https://agentmods.dev/badge/commands/croffasia/cc-blueprint-toolkit/execute-task/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/croffasia/cc-blueprint-toolkit/execute-task"><img src="https://agentmods.dev/badge/commands/croffasia/cc-blueprint-toolkit/execute-task.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.00008 | $0.00551 |
| Opus 5.5 | $0.00003 | $0.00220 |
| Sonnet 5.5 | $0.00002 | $0.00110 |
| Haiku 4.5 | $0.00001 | $0.00055 |
Grade A, and why
execute-task 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Development Task
Implement a specific development task using the detailed task specification.
Task File: $ARGUMENTS
Execution Process
-
Load Task Document
- Read the specified task breakdown file from
docs/tasks/ - Understand task context, requirements, and acceptance criteria
- Review all referenced files and code patterns
- Load the comprehensive task template structure
- Identify specific task within document if multiple tasks present
- Read the specified task breakdown file from
-
Task Analysis
- Extract the specific task requirements and constraints
- Review Given-When-Then acceptance criteria scenarios
- Study referenced code patterns and file locations
- Understand integration points and dependencies
-
Implementation Planning
- Use TodoWrite tool to create focused implementation plan
- Break down the single task into micro-steps if needed
- CRITICAL: Study all referenced files specified in task description
- PATTERN MATCHING: Identify exact patterns to mirror from existing code
- Plan implementation approach following established conventions
-
Focused Implementation
- BEFORE coding: Read reference files to understand exact structure
- MIRROR PATTERNS: Follow existing code patterns exactly
- Implement only the specific task requirements (no scope creep)
- Apply error handling patterns from reference implementations
- Follow code organization and naming conventions from examples
-
Acceptance Criteria Validation
- Execute each Given-When-Then scenario manually
- Verify rule-based criteria checklist completion
- Execute validation commands specified in task
-
Quality Gates
- Run project-specific validation commands
- Fix any linting, type-checking, or build errors
- Ensure task-specific Definition of Done criteria met
- Verify integration with existing systems
-
Task Completion
- Mark task as completed in TodoWrite
- Verify all acceptance criteria satisfied
- Document any implementation notes or gotchas discovered
- Report completion status with validation results
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 · 67 lines · 0 tokens per session scan A caa4756d3189
execute-task is a command published in the GitHub repository croffasia/cc-blueprint-toolkit (195 stars, last pushed 11mo ago), licensed MIT. It adds 8 tokens to every session and 551 once invoked, about $0.0000 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-30.
Other commands, from other repositories
cs-internal-comms
Internal-only change-management comms using ADKAR (Prosci) + Kotter's 8-step. NOT marketing (external) and NOT executive narrative strategy. Direct invocation of the internal-comms skill.
cs-knowledge-ops
Company SOP + runbook authoring with 5W2H completeness checks. NOT personal PKM (that's llm-wiki). NOT engineering-specific runbooks. Direct invocation of the knowledge-ops skill.
cs-process-map
Map an internal business process (BPMN-style swim lanes), measure cycle time, and detect bottlenecks where work spends most of its time waiting. Direct invocation of the process-mapper skill.
create-plan
Writes an implementation plan as a file artifact in the task directory (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, exact file changes and runnable success criteria, so reviewers comment on the file instead of in chat. Use when a task has its research done and needs a reviewable plan before code; pair with…
update-counts
Explicitly refresh public toolkit and committed marketplace source snapshots and numeric documentation.
paul:add-phase
Add a new phase to current milestone.