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 commands/dannykkh/skill-olympus/argosgit clone --depth 1 https://github.com/Dannykkh/skill-olympusWrote 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/commands/dannykkh/skill-olympus/argos)<a href="https://agentmods.dev/commands/dannykkh/skill-olympus/argos"><img src="https://agentmods.dev/badge/commands/dannykkh/skill-olympus/argos.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 | $0.00021 | $0.00407 |
| Opus 5 | $0.00010 | $0.00204 |
| Sonnet 5 | $0.00004 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
argos 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 3d 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.
What it actually says
/argos
설계 산출물(spec, api-spec, qa-scenarios, flow-diagrams) 대비 실제 구현을 검증합니다.
실행 절차
skills/argos/SKILL.md를 읽어 전체 워크플로우를 파악합니다.- 6단계 검증을 순서대로 실행합니다:
- Phase 0: CPS Traceability (Problem→Solution, Ecosystem→Section 매핑)
- Phase 1: Static Analysis (기능 요구사항 vs 코드, 비기능/품질)
- Phase 2: Runtime Verification (빌드, 단위 테스트, E2E)
- Phase 3: API Spec Verification (api-spec.md vs 실제 라우트)
- Phase 4: QA Scenario Checklist (qa-scenarios.md 항목별 통과/실패)
- Phase 5: Flow Diagram Verification (flow-diagrams/ 노드 매칭)
- Phase 6: Design Compliance (design-system.md 준수 + AI Slop + 0-10 채점)
- Phase 7: Security Review (시크릿 + 의존성 + OWASP + STRIDE)
- 결과를
<planning_dir>/verify-report.md에 저장합니다.
사용 예시
/argos # 자동 감지 (docs/plan/*/spec.md)
/argos @docs/plan/my-feature/ # 특정 planning_dir
/argos --phase 1 # 정적 분석만
/argos --skip-build # 빌드 검증 스킵
/argos --skip-e2e # E2E 검증 스킵
/argos --report-only # 기존 보고서 표시만
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.
- 3d ago First seen · 34 lines · 21 tokens per session scan A c16d4039d0d3
argos is a command published in the GitHub repository Dannykkh/skill-olympus (5 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 407 once invoked, about $0.0001 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 commands, from other repositories
rebuildrestart
Command "rebuildrestart" from rwliebs/Dossier, covering rebuildrestart, rebuild and restart the dossier dev server, usage and ./scripts/rebuild-and-restart.sh # dev server (default).
prune
Trim transcript clutter to extend session lifetime — analyze, prune a copy, or toggle the after-each-turn service. Dry-run by default; gains land at resume/compaction, not the current turn.
pr-description
Generate a PR title and description from the current branch diff against main.
conflict
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
amby.plan
Produce the technical implementation plan (the HOW) from an approved spec and UI.
clone
Runtime entry point for reverse-engineering an external website reference into a clean, code-native prototype design system.