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/iusztinpaul/squid/squid-implement-tasknpx skills add iusztinpaul/squid --skill squid-implement-taskgit clone --depth 1 https://github.com/iusztinpaul/squidWhat 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.00086 | $0.01653 |
| Opus 5 | $0.00043 | $0.00826 |
| Sonnet 5 | $0.00017 | $0.00331 |
| Haiku 4.5 | $0.00009 | $0.00165 |
Grade A, and why
squid-implement-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 3d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Task — inner SWE↔Tester loop (1 or N tasks)
Take a task (or a list of tasks / an approved Tasks Plan) and drive each one through the inner SWE → Tester loop, committing each task once it passes. This is the implementation core that /squid-implement-night runs; you can also run it standalone, on demand.
$ARGUMENTS is one of: a single task ref (NNN-slug / #N), a free-form task description, the feature's pending task files (tasks/<NNN>-*.md, status: pending), or several refs. If empty, ask the human what to implement.
You are the orchestrator — a MANAGER, not an implementer. You launch agents, enforce the Tester gate, and commit on green. You do NOT write code, run tests, or review the diff yourself beyond inspection (git diff, git log).
Read AGENTS.md first to confirm the active tracker mode (file or gh) and the project's stack + test commands.
Where this runs: in whatever working tree it's invoked in. When /squid-implement-night invokes it, it runs in the feature worktree /squid-plan created (the orchestrator passes Working directory: {path} to every agent). Standalone, it runs on your current branch. It does NOT create branches or worktrees — that's /squid-plan's job.
Critical rules:
- Never rubber-stamp the Tester. Spot-check that each AC marked PASS has real evidence (test name, file:line, command output) and that the e2e adversarial section actually attempted break paths. Re-launch with concrete feedback if not.
- One agent per task. Never bundle multiple tasks into one agent call.
- Commit each task on PASS — do NOT push. Pushing, PR creation, acceptance, and review are
/squid-review's job.
Step 1 — Resolve the task list
Build an ordered list of tasks from $ARGUMENTS:
- Tracker ref(s) (
NNN-slug/#N) → load each task'stasks/<NNN>-<slug>.md. - Approved Tasks Plan → the feature's
tasks/<NNN>-*.mdfiles withstatus: pending, inNNNorder (gh mode: the feature's open issues). - Free-form description → a single ephemeral task; don't create a task file unless the human asks.
- Empty → ask the human what to implement.
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.
- 3d ago First seen · 122 lines · 86 tokens per session scan A efc996644a9d
squid-implement-task is a skill published in the GitHub repository iusztinpaul/squid (184 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 86 tokens to every session and 1,653 once invoked, about $0.0004 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-30.
Other skills, from other repositories
ai-assist-prototype
Build self-contained, double-click-to-open HTML prototypes so the user can vet an interface before it gets built. One file holds several structurally different variants of a page, app screen, component, flow, or terminal/TUI layout (rendered in-browser), plus a draggable Design Deck for flipping between variants…
ai-assist-git-pr-review
Perform a standards-based code review on a GitHub Pull Request, then post the findings as inline review comments and mark the PR as 'Requested changes'. Reads all of the agents files that exist in the repository under review (AGENTS.md, .agents-docs/, CLAUDE.md on the PR's base branch) — the repo's full documented…
ai-assist-git-pr
Adaptive GitHub PR lifecycle skill — create PRs, write/update descriptions, investigate review comments (Copilot + human) with research and batch approval, and check merge readiness. Triggers on: create PR, open PR, describe PR, update description, PR body, check comments, copilot feedback, review comments, address…
ai-assist-changelog-bump
Validate and fix the CHANGELOG.md version number before opening a PR, commiting, or pushing changes, and keep package.json's version aligned with it. Reads main branch to determine the current latest version, classifies changes on the current branch, and proposes the correct next semver. Use this skill when the user…
ai-assist-design-creator
Reverse-engineer a website's visual design system from a URL and produce a fully spec-compliant DESIGN.md file (https://github.com/google-labs-code/design.md). The output includes both machine-readable YAML design tokens (colors, typography, spacing, rounded corners, components) and human-readable markdown rationale…
ai-assist-dockerize-website
Guide the user through containerizing and serving a simple website or documentation folder with Docker — inspects the project to detect what to serve (ready-to-serve static HTML, a buildable site that emits static output, or a raw markdown/docs folder that needs rendering), generates a Dockerfile, .dockerignore…