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/alonf/mcppythondemo/personal-squadnpx skills add alonf/MCPPythonDemo --skill personal-squadgit clone --depth 1 https://github.com/alonf/MCPPythonDemoWhat 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.00000 | $0.00464 |
| Opus 5 | $0.00000 | $0.00232 |
| Sonnet 5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
personal-squad 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 yesterday.
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
95% identical to personal-squad — 123 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.
What it actually says
Personal Squad — Skill Document
What is a Personal Squad?
A personal squad is a user-level collection of AI agents that travel with you across projects. Unlike project agents (defined in a project's .squad/ directory), personal agents live in your global config directory and are automatically discovered when you start a squad session.
Directory Structure
~/.config/squad/personal-squad/ # Linux/macOS
%APPDATA%/squad/personal-squad/ # Windows
├── agents/
│ ├── {agent-name}/
│ │ ├── charter.md
│ │ └── history.md
│ └── ...
└── config.json # Optional: personal squad config
How It Works
- Ambient Discovery: When Squad starts a session, it checks for a personal squad directory
- Merge: Personal agents are merged into the session cast alongside project agents
- Ghost Protocol: Personal agents can read project state but not write to it
- Kill Switch: Set
SQUAD_NO_PERSONAL=1to disable ambient discovery
Commands
squad personal init— Bootstrap a personal squad directorysquad personal list— List your personal agentssquad personal add {name} --role {role}— Add a personal agentsquad personal remove {name}— Remove a personal agentsquad cast— Show the current session cast (project + personal)
Ghost Protocol
See templates/ghost-protocol.md for the full rules. Key points:
- Personal agents advise; project agents execute
- No writes to project
.squad/state - Transparent origin tagging in logs
- Project agents take precedence on conflicts
Configuration
Optional config.json in the personal squad directory:
{
"defaultModel": "auto",
"ghostProtocol": true,
"agents": {}
}
Environment Variables
SQUAD_NO_PERSONAL— Set to any value to disable personal squad discoverySQUAD_PERSONAL_DIR— Override the default personal squad directory path
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.
- yesterday First seen · 58 lines · 0 tokens per session scan A 66bb192380ea
personal-squad is a skill published in the GitHub repository alonf/MCPPythonDemo (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 464 tokens. A static security scan graded it A with 0 findings. It is 95% identical to personal-squad, differing in 123 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…