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 luizvb/aquiles-skill --skill aquilesgit clone --depth 1 https://github.com/luizvb/aquiles-skillWrote 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/luizvb/aquiles-skill/aquiles)<a href="https://agentmods.dev/skills/luizvb/aquiles-skill/aquiles"><img src="https://agentmods.dev/badge/skills/luizvb/aquiles-skill/aquiles.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.00131 | $0.02541 |
| Opus 5 | $0.00066 | $0.01270 |
| Sonnet 5 | $0.00026 | $0.00508 |
| Haiku 4.5 | $0.00013 | $0.00254 |
Grade A, and why
aquiles 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 8d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aquiles
Own the outcome from uncertainty to a verified production release. Preserve specialist boundaries, externalize state, and make every handoff testable.
Core invariants
- Treat the target repository and its local instructions as the source of truth.
- Separate observed facts, user statements, assumptions, and recommendations.
- Never claim research, tests, browser checks, GitHub state, deploy state, or production behavior without direct evidence.
- Never expose secrets,
.envcontents, tokens, personal data, or private repository material in output, logs, commits, or marketing. - Distinguish technical access from mutation authorization. Authentication is not permission to push, create a remote, deploy, change DNS, or touch production.
- Do not let one specialist silently redefine another specialist's approved contract.
- Keep the smallest coherent scope that can prove the product thesis.
- Do not declare completion until the relevant release gates pass or the residual gaps are explicit.
- Treat a user-specified phase ceiling as a hard stop. Scaffolding may create blank reusable templates, but never populate or execute later phases beyond the authorized ceiling.
Start every run
- Read repository-level instructions such as
AGENTS.md,CLAUDE.md, contribution guides, and the current run or plan. - Resolve the target workspace. Preserve existing user changes and inspect the current Git state before editing.
- Use the host's canonical run protocol. If none exists, copy
assets/aquiles-run.mdto.aquiles/run.mdwithscripts/bootstrap_run.py. - For an empty greenfield workspace, prefer
scripts/bootstrap_product.py --workspace <target> --product <name>to create the complete starter evidence set. The script refuses overwrites and selects no product license by default; pass--license MIT --license-holder <holder>only when licensing is explicitly intended. - Execute
python3 scripts/preflight.py --workspace <target> --jsonfrom this skill directory. - Record an access matrix containing:
- Git repository, branch, worktree state, and remotes;
- GitHub CLI availability, authenticated account, and intended owner/repository;
- Vercel CLI availability, authenticated account, linked project, team/scope, and intended production target;
- whether
design-taste-frontendis installed; - explicit user authorization:
local_edits,commit,create_remote,push,preview_deploy,production_deploy,domain_or_env_changes.
- State the next bounded action and its evidence requirement before acting.
What ships with it
24 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 210 B
- assets/aquiles-run.md 7.5 KB
- assets/product-starter/.aquiles/design-contract.md 5.5 KB
- assets/product-starter/.aquiles/engineering-plan.md 6.4 KB
- assets/product-starter/.aquiles/fde-contract.md 5.9 KB
- assets/product-starter/.aquiles/launch-plan.md 4.8 KB
- assets/product-starter/.aquiles/opportunity.md 4.3 KB
- assets/product-starter/.aquiles/product-brief.md 3.9 KB
- assets/product-starter/.aquiles/release-record.md 5.6 KB
- assets/product-starter/.aquiles/test-report.md 5.7 KB
- assets/product-starter/.gitignore 81 B
- assets/product-starter/AGENTS.md 5.2 KB
- assets/product-starter/README.md 4.6 KB
- references/artifact-standards.md 15 KB
- references/design.md 3.5 KB
- references/engineering-release.md 6.3 KB
- references/marketing-growth.md 2.9 KB
- references/research-product.md 3.5 KB
- references/specialists.md 6.8 KB
- references/workflow.md 7.7 KB
- scripts/bootstrap_product.py 5.1 KB runs code
- scripts/bootstrap_run.py 1.7 KB runs code
- scripts/preflight.py 6.7 KB runs code
- scripts/privacy_scan.py 3.8 KB runs code
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.
- 8d ago First seen · 153 lines · 131 tokens per session scan A 688b49f07d1e
aquiles is a skill published in the GitHub repository luizvb/aquiles-skill (2 stars, last pushed 1mo ago), licensed MIT. It adds 131 tokens to every session and 2,541 once invoked, about $0.0007 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-31.
Other skills, from other repositories
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
github-tool
GitHub integration tool for listing and creating issues and PRs via the gh CLI wrapper. Use when: creating or listing issues or pull requests, or checking repository work on GitHub.
github-ops
GitHub repository operations — issues, PRs, code search, and config-as-code workflows. Use when creating a GitHub issue for a network finding, opening a pull request for a config change, searching repos for IP or VLAN references, or committing an audit report to a repository.
finn-build
Claim the next safe agent-ready issue from Linear, implement it, and open a PR. Use when asked to run Finn-loop's builder, work the approved queue, or fix Finn-loop review feedback. Designed for /loop; one pass does one unit of work.
finn-review
Review open PRs against their linked Linear issues and required GitHub checks, then post a three-group verdict with Finn-loop labels. Use when asked to run Finn-loop's reviewer or review its PR queue. Designed for /loop; never merges or pushes code.