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 0x0w1/jig --skill develop-task-flowgit clone --depth 1 https://github.com/0x0w1/jigWrote 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/0x0w1/jig/develop-task-flow)<a href="https://agentmods.dev/skills/0x0w1/jig/develop-task-flow"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/develop-task-flow/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/0x0w1/jig/develop-task-flow"><img src="https://agentmods.dev/badge/skills/0x0w1/jig/develop-task-flow.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.00077 | $0.02761 |
| Opus 5.5 | $0.00031 | $0.01104 |
| Sonnet 5.5 | $0.00015 | $0.00552 |
| Haiku 4.5 | $0.00008 | $0.00276 |
Grade A, and why
develop-task-flow 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 jig-develop-task-flow — 2 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop Task Flow
Use this repository skill for normal development work requested by the user.
Applies When
Installation is not adoption. jig can be installed user-global — a Claude Code user-scope plugin, a Codex plugin — and is then present in every repository on the machine, including ones that never took up this branch model. Being loaded here says nothing about how this repository works.
Adoption comes from repository instructions or an earlier explicit user decision to use jig's develop/main flow. Installing or loading jig, and branch names alone, do not establish that decision. Read the relevant repository policy; do not introduce a new configuration flag.
Check the branch prerequisites separately, using local and remote-tracking refs for both main and develop:
git show-ref --verify --quiet refs/heads/main || git show-ref --verify --quiet refs/remotes/origin/main
git show-ref --verify --quiet refs/heads/develop || git show-ref --verify --quiet refs/remotes/origin/develop
- Adopted, prerequisites present → use the branch model within Execution Scope.
- Not adopted, unclear, or prerequisites missing → complete authorized local work and verification under the repository's own workflow. Do not create
develop, infer approval to push, or replace that workflow. If committing was requested, follow its existing commit policy. Report any prerequisite that blocks an authorized landing;jig-setuporgithub-synccan establish the model when adoption/setup is requested.
Execution Scope
Distinguish four stages; permission for one does not imply later stages:
| Stage | What it does |
|---|---|
| 1. Edit and verify | requested file edits and relevant checks |
| 2. Commit | record task changes in Git |
| 3. Land | task branch, squash merge, push develop |
| 4. Release | promote, tag, publish via github-release |
Set the ceiling from the user's current request and repository policy they have explicitly approved:
- Current limits win. Local only, no commit, no merge, no push, or leave for review limits this task even under a standing landing policy. A review/diagnosis request authorizes inspection and reporting; edit files only when fixes are also requested. Implement/fix/update authorizes the work, but those verbs alone do not authorize committing or pushing.
- Reuse standing approval. If repository instructions already authorize committing and landing ordinary tasks, complete those stages without asking again unless the current request limits them. Adopting branch names alone is not that authorization. With no approval for a later stage, finish the authorized work and report it; do not make an optional commit/push question block local implementation.
- Release is separate. Stage 4 always needs an explicit release request and belongs to
github-release.
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 · +40 lines · +27 tokens per session 09a27255cee2
- 1mo ago First seen · 130 lines · 50 tokens per session scan A 249b93771002
develop-task-flow is a skill published in the GitHub repository 0x0w1/jig (5 stars, last pushed 20d ago), licensed MIT. It adds 77 tokens to every session and 2,761 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to jig-develop-task-flow, differing in 2 lines, and is treated as a copy.
Other skills, from other repositories
git-ship
An automated Git release workflow that takes code changes through a branch, commit, pull request, review checks, squash merge, and return to the main branch. A pull request is a request to review and merge changes into a shared branch.
worktree-pipeline-skill
Tracker-ticket-to-merged-PR pipeline via git worktrees — sync, plan, adaptive review, /run-plan, code review, PR merge. Triggers: run-worktree-pipeline, worktree pipeline, ticket to PR pipeline, tracker ticket pipeline.
semantic-release-convention-skill
Source of truth for commit-to-PR-to-merge-to-release conventions — semver labels, branch-aware tagging, changelogs, release pipelines.
version-bump-standard-skill
Consistent version bumping and release workflows — dev-to-uat-to-main flow, PR-label-driven semver. Use when setting up or auditing release workflows or onboarding a repo.
git-branch-workflow-setup-skill
Orchestrate dev-to-uat-to-main branch workflow setup during project init — detects need, prompts user via question tool, delegates to repo-ops-specialist-subagent.
git-semantic-commits-skill
Conventional Commits — type, scope, breaking changes, semver guidance, atomic-commit granularity by layer. Triggers: commit and push, make a commit, write a commit message, commit message format, semantic commit. Not for brevity (git-compact-commits-skill).