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 granoflow/granoflow-mcp-server --skill granoflow-task-authoringgit clone --depth 1 https://github.com/granoflow/granoflow-mcp-serverWrote 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/granoflow/granoflow-mcp-server/granoflow-task-authoring)<a href="https://agentmods.dev/skills/granoflow/granoflow-mcp-server/granoflow-task-authoring"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-task-authoring/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/granoflow/granoflow-mcp-server/granoflow-task-authoring"><img src="https://agentmods.dev/badge/skills/granoflow/granoflow-mcp-server/granoflow-task-authoring.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.00051 | $0.01217 |
| Opus 5 | $0.00026 | $0.00609 |
| Sonnet 5 | $0.00010 | $0.00243 |
| Haiku 4.5 | $0.00005 | $0.00122 |
Grade A, and why
granoflow-task-authoring 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 9d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Granoflow Task Authoring
Use this Skill to create Granoflow tasks with accurate titles and descriptions. It supports skeleton batches and single full creates. It does not run Task Work Analysis, Planning, execution, Delivery, or milestone charter/integration.
Prefer granoflow-portfolio-orchestrator when the user wants all milestones
created and then every milestone's tasks authored. Prefer
granoflow-task-orchestrator when the user wants lifecycle routing (analyze /
plan / run), not portfolio creation.
Keyword
#task-authoring#create-one#batch-skeleton
When To Use
- Create one task with a complete quality-checked description.
- Produce a skeleton portfolio table for one milestone, then create each task.
- Called by
granoflow-portfolio-orchestratorinside its per-milestone loop.
Required Reference
Before any create, read and apply
granoflow-agent-workflow/task-authoring-quality-contract. Failed quality
returns task_authoring_quality_failed for that task only; rewrite and retry
the same row—do not skip or widen the batch.
Also read references/task-authoring-modes.md. For UI milestones, also load
granoflow-agent-workflow/screen-task-portfolio-coverage and
granoflow-milestone-coordination/milestone-task-plan-template before treating
skeleton coverage as passed. Require Milestone task_plan.status: passed.
For every requirement-driven/software Milestone, load
granoflow-agent-workflow/milestone-ai-review and require schema v2 AI review
plus current digest before creating or continuing child tasks.
Modes
create_one
Author exactly one task's final title and description in this model turn,
run the quality contract, then create via App/API and read back. Never emit
multiple complete descriptions in one turn. Write back the App task_id onto
Milestone task_plan.tasks[].task_id for the matching local_key. Do not
bind tasks onto Project Work screen_coverage.
batch_skeleton
Emit a table of skeleton rows for one milestone (or an explicit small set).
Each row includes title draft, one-line responsibility, acceptance ids,
screen_ids (aligned with Milestone task_plan), depends_on, and
milestone_id. No full description bodies. Then run coverage checks against
mandatory acceptance ids and Milestone task_plan (passed status, split
probes, ≥1 skeleton row per refined screen).
What ships with it
2 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.
- 9d ago First seen · 135 lines · 51 tokens per session scan A e086b4592eb0
granoflow-task-authoring is a skill published in the GitHub repository granoflow/granoflow-mcp-server (0 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,217 once invoked, about $0.0003 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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.