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 iusztinpaul/squid --skill squid-implement-nightgit clone --depth 1 https://github.com/iusztinpaul/squidWrote 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/iusztinpaul/squid/squid-implement-night)<a href="https://agentmods.dev/skills/iusztinpaul/squid/squid-implement-night"><img src="https://agentmods.dev/badge/skills/iusztinpaul/squid/squid-implement-night/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/iusztinpaul/squid/squid-implement-night"><img src="https://agentmods.dev/badge/skills/iusztinpaul/squid/squid-implement-night.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.00052 | $0.01258 |
| Opus 5.5 | $0.00021 | $0.00503 |
| Sonnet 5.5 | $0.00010 | $0.00252 |
| Haiku 4.5 | $0.00005 | $0.00126 |
Grade A, and why
squid-implement-night 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.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Night — end-to-end feature pipeline (thin orchestrator)
Build an already-approved feature plan all the way to a validated, ready-to-merge PR. This skill is a thin orchestrator: the real work lives in the sub-skills it invokes — /squid-implement-task, /squid-review, /squid-review-ci — plus the agents those skills launch.
$ARGUMENTS is the approved Tasks Plan reference (path or feature slug) produced by /squid-plan. If empty, ask the human which plan to build (and remind them to run /squid-plan first if none exists).
You are the orchestrator — a MANAGER. You sequence the sub-skills, route rollback tasks, and enforce the gates. You do NOT write code, review the diff, or run tests yourself.
Read AGENTS.md first (tracker mode, the pipeline map, and the cross-cutting rules). Retry caps live in each sub-skill.
Input: an approved Tasks Plan + the feature branch/worktree /squid-plan created.
Output: a CI-validated feature PR, ready for the human to squash-merge.
The pipeline blocks on the human only at the very end (squash-merge). (Plan approval already happened in /squid-plan.) Everything between is automated; failures route back into /squid-implement-task as rollup tasks rather than stopping the pipeline. Caps stop the pipeline: Tester FAIL 5/task, PA REJECT 3, PR-Reviewer 3, On-Call 5 — when a cap fires, surface USER ACTION REQUIRED and stop.
Critical rules:
- Never rubber-stamp a sub-skill's result. When
/squid-reviewreports "no blockers" or/squid-review-cireports "green", confirm the evidence is real before advancing. - By name, never by path. Invoke
/squid-implement-task,/squid-review,/squid-review-ciby their skill names so it works when installed as a plugin.
Step 0 — Locate the branch worktree + tasks
/squid-plan created the feature branch feat/{slug} — either in a dedicated worktree at ../{repo}-{slug} or in the current working tree — and wrote the feature's task files (tasks/<NNN>-*.md, status: pending) on it. Find where that branch is checked out:
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 Changed · -17 lines · -12 tokens per session f3ac6d585adf
- 1mo ago First seen · 123 lines · 64 tokens per session scan A f95f25a6e869
squid-implement-night is a skill published in the GitHub repository iusztinpaul/squid (206 stars, last pushed 7d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,258 once invoked, about $0.0002 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
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-tech-debt
22-dimension, 5-tier technical debt audit covering code quality, architecture, infrastructure, quality processes, and operational readiness. Produces severity-ranked findings with weighted health score. Use when assessing codebase health, prioritizing tech debt remediation, or auditing code quality across all layers.
review-deployment
Apply when reviewing code or planning a deployment. Pre-merge checks, migration ordering, rollback strategy, post-deploy verification.
responding-to-feedback
Use when replying to feedback on your work (review comments, manuscript revisions, design critique, criticism).
green-prs
Inspect and prepare the selected PR queue against its exact current base, repair authorized defects with contributor credit, and report full versus partial validation. Use for maintainer pre-greening; merging requires separate owner authorization and the shared merge gates.