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 agentmods add skills/tu11aa/squadrant/squadrant-register-projectnpx skills add tu11aa/squadrant --skill squadrant-register-projectgit clone --depth 1 https://github.com/tu11aa/squadrantWrote 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/tu11aa/squadrant/squadrant-register-project)<a href="https://agentmods.dev/skills/tu11aa/squadrant/squadrant-register-project"><img src="https://agentmods.dev/badge/skills/tu11aa/squadrant/squadrant-register-project.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 | $0.00040 | $0.00449 |
| Opus 5 | $0.00020 | $0.00225 |
| Sonnet 5 | $0.00008 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
squadrant-register-project 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 4d 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
Register an Existing Project
Use when the repo already exists locally or on GitHub and you just need to register it in squadrant.
Step 1 — Resolve the local path
Local path given: use it directly.
GitHub URL given: clone first, then use the destination:
gh repo clone <org>/<repo> <dest-path>
Step 2 — Determine the project name
Default to the directory name:
basename <path>
Override if the directory name is ambiguous (e.g. src, app).
Step 3 — Determine group placement
List existing projects and their groups:
squadrant projects list
Then decide:
New group — pick a group name (kebab-case). This project will be primary automatically (first in group). No --group-role needed.
Existing group — pick the group name and specify a role that describes this project's purpose (e.g. "documentation site", "agent task queue", "shared skills library"). The role must NOT be "primary" — that slot is already taken by the first project in the group.
Note:
--group-roleonly auto-sets to"primary"when it is the first project registered in a group. All subsequent projects in the same group require an explicit--group-role.
Step 4 — Register
squadrant projects add <name> <path> \
--captain "⚓ <name>-captain" \
[--group <group-name>] \
[--group-role "<role description>"]
Omit --group and --group-role entirely if this is a standalone project with no group.
Step 5 — Verify
squadrant projects list
Confirm the new entry appears with the correct path, group, and role.
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.
- 4d ago First seen · 61 lines · 40 tokens per session scan A 3df67134db4b
squadrant-register-project is a skill published in the GitHub repository tu11aa/squadrant (2 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 449 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…