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 agents/dannykkh/skill-olympus/fullstack-coding-standardsgit clone --depth 1 https://github.com/Dannykkh/skill-olympusWhat 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.00051 | $0.03236 |
| Opus 5 | $0.00026 | $0.01618 |
| Sonnet 5 | $0.00010 | $0.00647 |
| Haiku 4.5 | $0.00005 | $0.00324 |
Grade A, and why
fullstack-coding-standards 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 253 lines · 51 tokens per session scan A 4ae4b3fcc472
fullstack-coding-standards is an agent published in the GitHub repository Dannykkh/skill-olympus (5 stars, last pushed 8d ago), with no licence file. It adds 51 tokens to every session and 3,236 once invoked, about $0.0003 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 agents, from other repositories
harness-optimizer
Self-optimization agent that analyzes the Hangar configuration (hooks, skills, rules, context modes, agents) and recommends improvements for reliability, performance, and token efficiency.
performance-optimizer
Active performance analysis agent. Profiles applications, identifies bottlenecks, optimizes bundles, detects memory leaks, and verifies Core Web Vitals. Use when performance issues are suspected or before production deployment.
security-reviewer
Quick security check for code and projects. Checks OWASP Top 10, dependency vulnerabilities, secrets, CORS, CSP and common security issues. Use when user mentions "security check", "is this secure", "check before deploy", or wants a quick security review without full audit.
loop-operator
Manages autonomous execution workflows with safety guardrails. Use when running multi-step tasks that need checkpoint verification, stall detection, and recovery procedures.
architect
Software architecture specialist for system design, scalability, and technical decisions. Use PROACTIVELY when planning new features, refactoring large systems, or making architectural decisions.
commit-reviewer
Pre-commit review for staged changes. Checks for debug code, secrets, missing tests and unintended files. Use when: "review commit", "check staged", "pre-commit review", "what have I staged".