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 carloshpdoc/ios-workflow-claude --skill create-tasksgit clone --depth 1 https://github.com/carloshpdoc/ios-workflow-claudeWrote 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/carloshpdoc/ios-workflow-claude/create-tasks)<a href="https://agentmods.dev/skills/carloshpdoc/ios-workflow-claude/create-tasks"><img src="https://agentmods.dev/badge/skills/carloshpdoc/ios-workflow-claude/create-tasks.svg" alt="Measured on agentmods" 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.00139 | $0.04663 |
| Opus 5 | $0.00069 | $0.02331 |
| Sonnet 5 | $0.00028 | $0.00933 |
| Haiku 4.5 | $0.00014 | $0.00466 |
Grade A, and why
create-tasks 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 7d 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 — 328 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project context: Values in angle brackets below (e.g.
<scheme>,<JIRA_KEY>,<flag-key-enum>) are resolved at runtime — detect them from the project (xcodebuild -list -jsonfor the scheme,git/ghfor repo & owner, the branch name for the Jira key, a codebase search for flag/font files), or ask if they cannot be inferred. This plugin ships no per-project config.
Create Tasks from Meeting Notes / Specs
Take meeting notes, specs, or a feature description as input. Detect the platform, explore the codebase, plan the implementation, and create Jira tickets.
Usage
/create-tasks <description or paste meeting notes>
$ARGUMENTS— Feature description, meeting notes, specs, or any context about work to be planned
Platform Detection
Detect the platform automatically from the current repository:
| Signal | Platform |
|---|---|
Package.swift, *.xcodeproj, Tuist/, *.swift files |
iOS |
package.json, tsconfig.json, src/api/, serverless.yml |
Backend |
If ambiguous (e.g., meeting notes mention both platforms), ask the user which platform to create tasks for — or create tasks for both if explicitly requested.
Jira Configuration (Shared)
- Project: <JIRA_KEY>
- Issue type: Task
- Story points field:
customfield_10034 - Allowed story point values: 1, 2, 3 only
- Board: https:///jira/software/c/projects/<JIRA_KEY>/boards//backlog
- Epic: Link tasks to an epic via
"parent": "<EPIC-KEY>"inadditional_fields. Ask the user which epic to use if not specified. - Assignee: Ask the user who to assign tasks to before creating tickets. Use email or display name for the
assigneefield. - Sprint: Default to the current active sprint. Fetch via
mcp__mcp-atlassian__jira_get_sprints_from_board(board ID<jira-board-id>, stateactive). Set via"customfield_10020": <sprint_id>inadditional_fields. If no active sprint or the user specifies a different one, ask for input. - Next sprint (for feature flag cleanup tickets): Fetch via
mcp__mcp-atlassian__jira_get_sprints_from_board(board ID<jira-board-id>, statefuture) and take the first result. If no future sprint exists yet, ask the user whether to create the cleanup ticket in the backlog (omitcustomfield_10020) or wait.
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.
- 7d ago First seen · 328 lines · 139 tokens per session scan A 1945dff2ed02
create-tasks is a skill published in the GitHub repository carloshpdoc/ios-workflow-claude (7 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 139 tokens to every session and 4,663 once invoked, about $0.0007 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
feedback
A feedback-management skill from the Reqord project, including commands for handling feedback and checking the repository.
status
A Reqord progress dashboard for requirements and specifications. It groups work by status and lists design-document readiness and unresolved feedback.
new
A Reqord workflow for creating new data records. It handles command arguments, reference resources, and errors when adding information to Reqord, a requirements-management tool.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
ijfw-plan
Use when the user says 'plan this', 'plan it', 'make a plan', 'let's plan', 'draft a plan', 'how should we tackle this', 'break this down', or invokes '/ijfw-plan'. Produces a falsifiable PLAN.md (software, book, campaign, design, research) with task breakdown, dependency wave-table, and success criteria — gated by…
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".