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 sync-tasksgit 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/sync-tasks)<a href="https://agentmods.dev/skills/mimfort/rag_for_git/sync-tasks"><img src="https://agentmods.dev/badge/skills/mimfort/rag_for_git/sync-tasks/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/sync-tasks"><img src="https://agentmods.dev/badge/skills/mimfort/rag_for_git/sync-tasks.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.00036 | $0.00623 |
| Opus 5.5 | $0.00014 | $0.00249 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00062 |
Grade A, and why
sync-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 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.
What it actually says
Sync Tasks
Reply in Russian. This is a thin, server-side trigger: the server enumerates, normalizes, and indexes the board. Do not enumerate tasks in the client and do not send credentials.
-
Resolve the repository path with
git rev-parse --show-toplevel, then rungit -C <path> remote get-url origin. For HTTPS and SSH URLs, remove the scheme, userinfo, and host; for scp-style remotes, remove everything through the host's first colon. Preserve every path segment after the host or scp colon, remove the leading slash, strip a trailing.git, then lowercase and validate the result as the canonical lowercase repository id (owner/nameorgroup/.../name). Examples:https://gitlab.example.com/group/sub/repo.git→group/sub/repossh://[email protected]/group/sub/repo.git→group/sub/repo[email protected]:group/sub/repo.git→group/sub/repo
If origin is missing or ambiguous, ask for the complete namespace/repo id; do not guess from the directory name.
-
Resolve branch independently. Pass a non-null branch only when the user explicitly supplied or selected one and it is in the tracked branches list (
REVIEW_BRANCHES). With no explicit tracked selection, passbranch=nullso the server uses its primary tracked branch. Never infer the branch from the current worktree branch or blindly pass an untracked feature branch. -
Call only repo mode with operation flags. The server owns effective board-policy resolution; do not reconstruct policy in the client:
sync_board(repo=<canonical owner/name or group/.../name>, branch=<explicit tracked branch or null>, limit=<limit or null>, purge_orphaned=<explicit request or false>, keep_with_prs=<explicit request or true>, force_renormalize=<explicit request or false>) -
If the result is a configuration or policy error, explain it in Russian and stop. Do not retry through unfiltered explicit mode: that could enumerate or purge the wrong task corpus.
-
Report the server-side summary in Russian, including
eligible,filtered_by_age,filtered_archived,age_unknown,archive_unknown,filter_applied,filter_fingerprint,filter_source,by_board,purge, andwarnings. Explain warnings and leave the local repository unchanged.
sync_board is idempotent: rerunning is safe and inexpensive when the watermark is warm. It reads
the board; it never writes back.
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 · 48 lines · 36 tokens per session scan A 62343d6f92e8
sync-tasks is a skill published in the GitHub repository mimfort/rag_for_git (20 stars, last pushed 6d ago), licensed MIT. It adds 36 tokens to every session and 623 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
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…