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 taylorparsons/athena-skill --skill athenagit clone --depth 1 https://github.com/taylorparsons/athena-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/taylorparsons/athena-skill/athena)<a href="https://agentmods.dev/skills/taylorparsons/athena-skill/athena"><img src="https://agentmods.dev/badge/skills/taylorparsons/athena-skill/athena/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/taylorparsons/athena-skill/athena"><img src="https://agentmods.dev/badge/skills/taylorparsons/athena-skill/athena.svg" alt="Reviewed on agentmods" width="80" 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.00055 | $0.01350 |
| Opus 5 | $0.00028 | $0.00675 |
| Sonnet 5 | $0.00011 | $0.00270 |
| Haiku 4.5 | $0.00006 | $0.00135 |
Grade A, and why
athena 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 9d 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.
This is a copy
100% identical to athena — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ATHENA Loop
The audit trail lives in docs/ but is script-gated: never Read docs/requests.md, docs/decisions.md, docs/athena-index.md, or archived specs — all access goes through ./scripts/owl (deterministic, zero-token). You may Read/Edit directly only:
- the active feature's
docs/specs/<FEATURE_ID>/spec.md,tasks.md,notes.md - the
docs/PRD.mdsections you are changing — never the full file: locate the section with grep, read only that line range; one requirement →owl show <FR-ID> docs/TRACEABILITY.md
1) Open the session
- Claude Code: if the
Athena Active Contextmemory is present, use it and skip the next step. - Otherwise run
./scripts/owl context— prints active feature, goal, IN PROGRESS/NEXT, recent CR/D IDs, and the latest request. - Repo has no
docs/audit files, or still hasdocs/progress.txt? Seereferences/setup.md. - Summarize the session goal in one sentence before changing anything.
2) Capture input first
No PRD or code changes until the session's customer request is captured verbatim (redact secrets):
./scripts/owl add-request <<'EOF'
<verbatim customer request>
EOF
Returns the CR-... ID. No explicit request this session? Ask the user for one.
Whenever you interpret ambiguity, choose tradeoffs, or change scope:
./scripts/owl add-decision --cr <CR-ID> --prd "<PRD section>" <<'EOF'
Decision: <what>
Rationale: <why>
Alternatives considered: <rejected options and why>
EOF
3) Reflect in PRD and spec
- If the newest CR is not reflected in
docs/PRD.md, update the PRD first. Tag every added or changed requirement(Sources: CR-...; D-...)— at least one CR, plus a D whenever interpretation was needed. - Establish a FEATURE_ID (
YYYYMMDD-short-name; ask if unclear). Ensuredocs/specs/<FEATURE_ID>/spec.mdandtasks.mdexist (copy fromtemplates/). - Traceability is mandatory: FRs have stable IDs and
Sources:; acceptance scenarios haveVerifies: FR-...; tasks haveImplements: FR-.... Fix broken links before writing code.
What ships with it
20 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 317 B
- agents/owl-of-athena.md 2.1 KB
- assets/athena-warrior-icon.svg 1.3 KB
- references/commits.md 1.4 KB
- references/recovery.md 760 B
- references/setup.md 2.1 KB
- scripts/bootstrap_git_audit.py 4.0 KB runs code
- scripts/commit_with_traceability.py 11 KB runs code
- scripts/owl.py 51 KB runs code
- scripts/print_resume_prompt.py 4.9 KB runs code
- scripts/progress_schema.py 3.5 KB runs code
- scripts/tests/test_owl.py 11 KB runs code
- scripts/validate_progress_log.py 1.3 KB runs code
- scripts/validate_traceability_links.py 7.4 KB runs code
- templates/decisions.md 368 B
- templates/notes.md 274 B
- templates/requests.md 188 B
- templates/spec.md 646 B
- templates/tasks.md 249 B
- templates/traceability.md 1.0 KB
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.
- 9d ago First seen · 88 lines · 55 tokens per session scan A 20703f98ca6a
athena is a skill published in the GitHub repository taylorparsons/athena-skill (2 stars, last pushed 4d ago), licensed MIT. It adds 55 tokens to every session and 1,350 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to athena, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
project-graveyard
Scans the developer's machine for dead side projects, autopsies each one from its git history (died at the payments wall, killed by a newer project, finished but never shipped), surfaces their personal death patterns, and picks the corpse most worth resurrecting — then helps ship it. Use when the user mentions…
commit-archaeologist
Reconstructs why code exists from local git history, including the introducing commit, later changes, current authors, repeated companion files, and likely intent. Use when the user asks "why does this code exist", "who wrote this function and why", or to "explain the history of this function" before a rewrite…
scope-creep-detector
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad pull requests, changes that grew beyond a fix, dependency additions, public API renames, config or CI edits, oversized hunks, and formatting-only files. Use when the user asks whether a change grew beyond the fix, a PR is too…
git-workflow
Git workflow guidance for commits, branches, and pull requests.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
marimo-pair
Work inside the user's live marimo notebook from the code editor: run Python in the same kernel the user does, inspect live notebook state, and commit durable notebook changes through code mode. Use whenever you create, analyze, or improve the user's marimo notebook.