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 mimfort/rag_for_git --skill decompose-taskgit clone --depth 1 https://github.com/mimfort/rag_for_gitWrote 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/mimfort/rag_for_git/decompose-task)<a href="https://agentmods.dev/skills/mimfort/rag_for_git/decompose-task"><img src="https://agentmods.dev/badge/skills/mimfort/rag_for_git/decompose-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/skills/mimfort/rag_for_git/decompose-task"><img src="https://agentmods.dev/badge/skills/mimfort/rag_for_git/decompose-task.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.02393 |
| Opus 5.5 | $0.00007 | $0.00957 |
| Sonnet 5.5 | $0.00003 | $0.00479 |
| Haiku 4.5 | $0.00002 | $0.00239 |
Grade A, and why
decompose-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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Decompose Task
Overview
Reply in Russian. Build one grounded, reviewable native-subtask batch; no child may reach the board before the user sees the entire batch. Core principle: preview fidelity and durable idempotency are safety boundaries, not optional ceremony.
Lookup
The stored parent and authoritative native_subtasks capability are required gates.
- Inspect the repository
task_boardkey once and resolve exactly one state:- If the key is present with a null, empty, or disabled value, board work is explicitly
disabled: stop no-write and never call deploy-wide
get_board_config. - Only if the repository key is absent, use the deploy fallback: call
get_board_config()exactly once. - If a mapping exists, freeze its generic
type,project, andoptionsasboard_type,project, andprovider_optionsfor the whole flow. Never re-resolve mid-flow. If no mapping resolves, stop without writes.
- If the key is present with a null, empty, or disabled value, board work is explicitly
disabled: stop no-write and never call deploy-wide
- Read the store first with
get_task(parent_key, project=<project>). On miss only, run exactly one scopedsync_board(board=<project or null>, board_type=<type>, provider_options=<options>), then make one retry of the same parent read. If it is still missing, explain the failure and stop. - Call
get_board_targets(board_type=<type>, project=<project>, provider_options=<options>). Treat its registrycapabilitiesas authoritative. If it errors or lacksnative_subtasks, make a no-write stop. Never infer, add, or spoof a capability from provider identity or prior experience.
Context
Before drafting, attempt all three calls:
get_task_context(parent_key, project=<project>)for links, related work, PRs, and touched code;search_tasks(query=<parent intent>, project=<project>)for similar decomposition boundaries;search_codebase(repo=<active repo>, query=<parent intent>)for relevant implementation and realpath:lineevidence.
Empty successful results are allowed: explicitly report each empty result and continue. A tool error is not an empty result; report it and stop drafting until resolved. Do not draft first and backfill evidence later.
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 · 193 lines · 17 tokens per session scan A 8d6adcc54a34
decompose-task is a skill published in the GitHub repository mimfort/rag_for_git (20 stars, last pushed 6d ago), licensed MIT. It adds 17 tokens to every session and 2,393 once invoked, about $0.0001 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 skills, from other repositories
code-knowledge-graph
Codebase'i knowledge graph olarak analiz et. Dependency, call graph, hotspot analizi.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
coograph-review
Strict read-only review of the current changes for spec compliance, convention violations, logic bugs, and architecture. Every finding cites a verbatim quote from a fresh file read. Use after implementation, before declaring done.
graphenium
Use when analyzing codebase structure, verifying pre-flight policy compliance, tracing transitive dependency closures, or auditing post-edit scope creep.
celmis-search
Search and read code through Celmis instead of grepping or cat-ing whole repositories. Use when you need where a symbol is defined, who calls it, what a file or module contains, how another service does something ("make a DB connection like in service X", "do authorization the way service X does", "how does X load its…
autoreview
Structured code review through the shared OpenClaw agent-skills installation.