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-nightnpx 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.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.1 | $0.00052 | $0.01258 |
| Opus 5 | $0.00026 | $0.00629 |
| Sonnet 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 today.
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.
- today Changed · -17 lines · -12 tokens per session f3ac6d585adf
- 6d 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 (184 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 1,258 once invoked, about $0.0003 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
gh-fix-ci
Use when a user asks to debug or fix failing GitHub PR checks that run in GitHub Actions; use gh to inspect checks and logs, summarize failure context, draft a fix plan, and implement only after explicit approval. Treat external providers (for example Buildkite) as out of scope and report only the details URL.
latex-submission-pipeline
Use when building a LaTeX manuscript submission pipeline with templates, latexmk, BibTeX/Biber, chktex, latexindent, CI PDF builds, compile debugging, and submission zip packaging.
dev-branch-deploy
Drive the Hermes/Maia Concourse dev-branch deploy workflow — test stack changes in a live lab before merging to master. Use for "dev branch", "deploy to dev", "hermes-dev-branch", "maia-dev-branch", "test in labs", "dev lane". Covers both the hermes and maia stacks.
ci
Detect/generate/debug CI pipeline config (GitHub Actions, GitLab CI). Triggers: CI setup, build pipeline, GitHub Actions config, debug CI, GitLab CI.
azure-devops
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check…
ci-scaffolding
This skill should be used when the user says "set up CI", "create GitHub Actions", "scaffold CI pipeline", "add CI/CD", "configure continuous integration", "create test workflow", "create release workflow", "add pre-commit hooks", "set up linting pipeline", "configure ruff in CI", "configure biome in CI", "add typo…