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 makifbaysal/tasktrooper --skill project-repo-managementgit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/project-repo-management)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/project-repo-management"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/project-repo-management/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/makifbaysal/tasktrooper/project-repo-management"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/project-repo-management.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.00033 | $0.00479 |
| Opus 5.5 | $0.00013 | $0.00192 |
| Sonnet 5.5 | $0.00007 | $0.00096 |
| Haiku 4.5 | $0.00003 | $0.00048 |
Grade A, and why
project-repo-management 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 8d 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
Project & Repository Management
Overview
You own workspace organization, not just the board. Organize actions are factual and reversible — act directly and confirm, don't route them through analiz or approval.
Core principle: Organize requests are direct actions: call the tool, confirm with real names.
The tools
| Tool | Use |
|---|---|
create_project(name, description) |
Open a new initiative project when the stakeholder starts a new product/initiative or asks to group work |
update_project(project_id, name?, description?) |
Rename or edit a project's description (empty fields stay unchanged); get the id from list_projects first |
set_repository_projects(repository_id, project_ids) |
Link a repo to one or more projects (replaces existing links; empty list unlinks); get ids from list_repositories and list_projects |
Rules
- For a factual/organize request, act directly — no analiz, no approval. Call the tool, then confirm with real names ("Created the Alpha project and linked the X repo to it.").
- You cannot create a code repository's filesystem directory. If a brand-new repo is needed, tell the stakeholder to open it from the Repositories screen, then link it with
set_repository_projects.
Worked Example
Stakeholder: "Open a new 'Reporting' initiative and link the web repo to it."
create_project("Reporting", "...")→ get the new id.list_repositories→ find the web repo's id.set_repository_projects(webRepoId, [reportingId]).- Confirm: "Opened the Reporting project and linked the web repo to it."
Common Mistakes
- Opening an analiz task for a rename.
- Asking approval for a factual organize action.
- Claiming you can create the repo directory (you can't — direct the stakeholder to the Repositories screen).
Red Flags
- An analiz task titled "create a project."
- A
set_repository_projectscall with ids you guessed instead of looked up.
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.
- 8d ago First seen · 45 lines · 33 tokens per session scan A 328acffe619c
project-repo-management is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 479 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-10-05.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
standup-update
Generate a concise standup update from the user's recent work GitHub activity, including the previous work period and today. Use when the user asks what they worked on, requests a standup update, or invokes /standup.
paperclip
Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.
paperclip-board
Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
summarize-status
Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.