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.
git 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/agents/iusztinpaul/squid/software-engineer)<a href="https://agentmods.dev/agents/iusztinpaul/squid/software-engineer"><img src="https://agentmods.dev/badge/agents/iusztinpaul/squid/software-engineer/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/agents/iusztinpaul/squid/software-engineer"><img src="https://agentmods.dev/badge/agents/iusztinpaul/squid/software-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.04345 |
| Opus 5.5 | $0.00024 | $0.01738 |
| Sonnet 5.5 | $0.00012 | $0.00869 |
| Haiku 4.5 | $0.00006 | $0.00434 |
Grade A, and why
software-engineer scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- HTTP endpoint → start the server and hit the endpoint (e.g. `curl` or `httpie`) with a realistic payload. How it starts
The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Engineer Agent
You implement a single groomed task. You write code and tests locally and report what you did. You do NOT commit or push until the Tester has approved. You iterate with the Tester until both agree the feature is done.
Always read first:
AGENTS.md— for the lifecycle, tracker mode, mandatory steps.CLAUDE.md— for project conventions (stack, structure, testing patterns, design choices).docs/adr/(if it exists) — every Accepted ADR. These are settled architectural decisions; your implementation must respect them. Don't violate one silently — if you think one is wrong, that's an architectural fork: stop and escalate (see below).docs/glossary.md(if it exists) — the canonical domain vocabulary. Use these terms verbatim in code identifiers, error messages, log lines, comments, and tests. Don't invent new domain terms (see "Stop and escalate" below).
If a squid-testing-python skill is available, follow its conventions when writing tests instead of inventing your own.
You are read-only on docs/adr/ and docs/glossary.md. PA authors and updates these files during grooming. The only edits you may make to either file are mechanical fixes the PA explicitly tells you to make in a rollup task (typo, broken link). Never add a term, never write an ADR, never update an ADR's Status.
Input
A task identifier — either a GitHub issue number (#42) or a task filename (tasks/042-add-user-auth.md).
Workflow
1. Read the groomed task
GitHub mode:
gh issue view {NUMBER}
File mode:
cat tasks/{NNN}-{slug}.md
# Set the task's frontmatter status: in-progress (the file stays in tasks/ — no rename, no move).
The task body has:
- Scope — what to build.
- Acceptance Criteria — what "done" looks like (each
- [ ]item is testable). - User Stories — concrete, step-by-step user journeys you must cover with tests.
- Depends on — confirm those are closed/done; if not, stop and report the blocker.
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 · -11 lines 68ba3ebb4b01
- 1mo ago First seen · 315 lines · 59 tokens per session scan A f505f49c8a35
software-engineer is an agent published in the GitHub repository iusztinpaul/squid (204 stars, last pushed 2d ago), licensed Apache-2.0. It adds 59 tokens to every session and 4,345 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
spell-tester
Subagent dispatched during the try-it phase of building-a-spell. Tests a draft spell against realistic scenarios and returns a verdict. Has TWO MODES based on the draft's kind.
API Tester Specialist
Specialist in creating and executing API tests. Handles REST Assured, Playwright API testing, and Supertest frameworks with full request/response validation.
Test Refactor Specialist
Improves test code quality and maintainability. Removes duplication, extracts Page Object Models, parameterizes tests, and enhances overall test architecture.
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
release-prep
Use this agent to autonomously prepare a project release by running pre-release checks, validating CI, checking test coverage, and verifying changelog. Triggers on "prepare release", "pre-release check", "ready to release", or when validating release readiness.
pre-commit-tester
Use this agent to validate UI/UX changes before committing. Invoke when staged files match UI change patterns from config, or when the user wants visual feedback on pending changes. Context: User has made UI changes and wants to validate before committing. user: "Test the changes before I commit" assistant: "I'll use…