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/argos-ci/argos-javascript/argos-clinpx skills add argos-ci/argos-javascript --skill argos-cligit clone --depth 1 https://github.com/argos-ci/argos-javascriptWhat 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 | $0.00143 | $0.02617 |
| Opus 5 | $0.00072 | $0.01308 |
| Sonnet 5 | $0.00029 | $0.00523 |
| Haiku 4.5 | $0.00014 | $0.00262 |
Grade A, and why
argos-cli 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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Argos CLI
Run argos <command> --help for the exact flags of any command. This skill
covers only what --help can't: the token model, the output contract, and the
command map.
Output contract (agents)
- Pass
--jsonwhenever you parse stdout; commands print human-readable text otherwise. - Errors go to stderr as
Error: <message>. Exit0= success,1= failure. - Never print token values.
Authentication
A <buildReference> is a build number (e.g. 72652) or a full build URL. With a
number, add --project owner/project; a URL already contains it. A <changeId>
is not a build ref: it comes from a diff's change.id and does not carry the
account, so every change command needs --project owner/project (or
ARGOS_PROJECT). A <testId> comes from a diff's test.id and carries the
project name but not the account, so test commands need the same
--project/ARGOS_PROJECT — except with a project token, which already
identifies its own project. project and automation commands take the same
--project owner/project; account commands take --account <slug> (or
ARGOS_ACCOUNT).
Two token types — pick by command:
| Commands | Token | Resolution order |
|---|---|---|
build get, build snapshots, test list, test get, test changes, change list, project get, project deployments, project domain get, media get, media list, media versions, media update, media delete |
Project token | --token › ARGOS_TOKEN |
review *, comment *, test comment *, media comment *, test subscribe / unsubscribe, build subscribe / unsubscribe, change ignore / unignore, account *, project update, project transfer, project contributor *, project domain set, automation *, analytics, create-project |
Personal access token (PAT) | --token › ARGOS_TOKEN › argos login |
upload, finalize, skip, deploy, media upload |
CI / project token | --token › ARGOS_TOKEN (or tokenless CI) |
What ships with it
1 file 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.
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.
- 2d ago First seen · 163 lines · 143 tokens per session scan A 70aacf9c8e9c
argos-cli is a skill published in the GitHub repository argos-ci/argos-javascript (18 stars, last pushed 6d ago), licensed MIT. It adds 143 tokens to every session and 2,617 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-30.
Other skills, from other repositories
write-gitbook
A comprehensive guide for editing GitBook documentation in external environments like Cursor, Claude Code, or other text editors. This skill provides all the formatting syntax, configuration options, and best practices needed to create and maintain GitBook content outside the GitBook web interface.
documentation-writer
Diátaxis Documentation Expert. An expert technical writer specializing in creating high-quality software documentation, guided by the principles and structure of the Diátaxis technical documentation authoring framework.
keploy-docs
Guide for contributing to the Keploy documentation site at github.com/keploy/docs. Invoke when a change in keploy/keploy introduces, removes, or alters user-visible behavior (new CLI flag, changed default, new command, new configuration field, new on-disk format) and the docs need to catch up — or when the user asks…
wxjava-api-contributor
按 WxJava 的 Maven 多模块、Java 8、公共 API 兼容性和 TestNG 约定，为微信官方接口新增或维护 SDK 支持。适用于新增 Service API、请求响应 Bean、序列化、HTTP 实现、Starter 配置或回归测试时。.
wxjava-troubleshooter
排查 WxJava 在配置初始化、access token、签名验签、支付证书、回调通知、序列化、网络请求和多账号隔离方面的问题。适用于用户提供异常、日志、请求响应或“WxJava 为什么不能调用”的场景。.
wxjava-upgrade-guide
规划 WxJava 的版本升级与迁移，检查 BOM、模块依赖、Java 版本、配置与公共 API 兼容性，并提供可回滚的验证步骤。适用于用户从旧版升级、切换依赖管理方式、处理兼容性告警或制定升级发布计划时。.