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 get-tmonier/argot --skill argot-setup-cigit clone --depth 1 https://github.com/get-tmonier/argotWrote 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/get-tmonier/argot/argot-setup-ci)<a href="https://agentmods.dev/skills/get-tmonier/argot/argot-setup-ci"><img src="https://agentmods.dev/badge/skills/get-tmonier/argot/argot-setup-ci.svg" alt="Measured on agentmods" 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.00094 | $0.01556 |
| Opus 5 | $0.00047 | $0.00778 |
| Sonnet 5 | $0.00019 | $0.00311 |
| Haiku 4.5 | $0.00009 | $0.00156 |
Grade A, and why
argot-setup-ci 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
argot-setup-ci
Add argot to a repository's CI as a non-blocking pattern check on every pull request. Never make it block the merge unless the user explicitly asks for a gate. This is user-wired automation: the Action runs only at the GitHub event in the workflow the repository commits; it does not install or claim an agent end-of-turn or acceptance lifecycle.
The Action installs Argot but never fits in CI. CI and local setup are one
decision: a committed argot.toml plus a complete committed .argot/ fit
snapshot already on the PR base/default branch — the excludes and learned
detector data that keep every check reproducible. A repository without that
snapshot must run the full
argot-setup flow first. The excludes
that keep vendored, generated and demo trees out of the voice — makes the CI
voice sharper, and argot is only as good as that scoping. If the repository
has no argot.toml yet, offer the full argot-setup
flow first, which covers CI as one of its phases. Come here when the user
wants CI specifically, or already has a configured repo.
Steps
-
Confirm the repo is on GitHub. (Forks: enable Actions in Settings first.)
-
Check the bootstrap boundary before writing a workflow. On the branch that future pull requests will target (normally the default branch),
argot status --format jsonmust showsnapshot.complete: trueandsnapshot.committed: true. Verify the tracked artifact is available from that branch, for example:git show HEAD:.argot/scorer-config.json > /dev/nullA snapshot committed only in the PR adding the workflow does not satisfy this: the Action reads the PR base so a change cannot certify itself. If it is absent, finish, review, commit, and merge the baseline first; add CI in a follow-up PR or commit. Do not use CI fitting as a workaround.
-
Write
.github/workflows/argot.yml:name: argot on: pull_request: push: branches: [main] permissions: contents: read pull-requests: write # the sticky score comment security-events: write # SARIF code-scanning annotations jobs: voice: runs-on: ubuntu-latest steps: - uses: actions/checkout@v4 with: fetch-depth: 0 # Action reads the committed snapshot from the PR base - uses: get-tmonier/argot@main
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 · 132 lines · 94 tokens per session scan A 5f22aacff44c
argot-setup-ci is a skill published in the GitHub repository get-tmonier/argot (48 stars, last pushed 6d ago), licensed MIT. It adds 94 tokens to every session and 1,556 once invoked, about $0.0005 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
Code Coverage Analysis
Measure and enforce test coverage with Istanbul/nyc, c8, Jest, and Vitest. Covers branch versus line coverage, per-directory thresholds, CI gates, and correctly excluding generated code from reports.
supply-chain
Use when auditing security and supply chain in any codebase — trust boundaries, credential handling, injection surfaces, update/release integrity, CI permissions, dependency pinning. Assess by default, harden on request; provenance or it didn't happen.
deployment
Use when taking an app from source to live: choosing the deploy target from requirements (Hetzner+Coolify vs Vercel vs a third), then wiring container → CI → registry → host with build secrets, healthchecks and rollback. NOT one platform's mechanics (that is coolify, vercel, railway, render), NOT the Dockerfile alone…
verify
Pre-merge verification gate. Build, test, and lint must all pass before marking done or shipping.
diagnose-ci-failures
Diagnose failing CI, lint, typecheck, build, or test logs and propose or implement the smallest verified fix.
audit-harness
Use when auditing HARNESS.md, pre-commit hooks, pre-push hooks, architecture gates, or CI workflows for tunacode-cli. This skill treats any mismatch, skipped gate, or failing check as a critical failure and requires manual one-by-one execution rather than make targets, batch wrappers, or summary-only audits.