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 ils15/pantheon-legacy --skill artifact-managementgit clone --depth 1 https://github.com/ils15/pantheon-legacyWrote 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/ils15/pantheon-legacy/artifact-management)<a href="https://agentmods.dev/skills/ils15/pantheon-legacy/artifact-management"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/artifact-management/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/ils15/pantheon-legacy/artifact-management"><img src="https://agentmods.dev/badge/skills/ils15/pantheon-legacy/artifact-management.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00759 |
| Opus 5.5 | $0.00008 | $0.00304 |
| Sonnet 5.5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
artifact-management 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 1mo 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Management
Structured artifact trail system for documenting feature implementations. Defines what, where, and how agents produce phase outputs.
Temp Folder
All ephemeral artifacts live in .pantheon/memory-bank/.tmp/ — gitignored and wiped on sprint close.
.pantheon/memory-bank/
├── .tmp/ ← GITIGNORED — ephemeral artifacts
│ ├── PLAN-<feature>.md
│ ├── IMPL-phase1-hermes.md
│ ├── IMPL-phase1-aphrodite.md
│ └── REVIEW-<feature>.md
├── _notes/ ← COMMITTED — permanent ADRs
│ └── ADR-<topic>.md
├── 01-active-context.md
└── 02-progress-log.md
Artifact Types
| Prefix | Location | Ephemeral? | Produced by |
|---|---|---|---|
PLAN- |
.tmp/ |
✅ | Athena |
IMPL- |
.tmp/ |
✅ | Hermes/Aphrodite/Demeter |
REVIEW- |
.tmp/ |
✅ | Themis |
DISC- |
.tmp/ |
✅ | Apollo |
ADR- |
_notes/ |
❌ Permanent | Any → Mnemosyne |
Who Generates
| Situation | Agent | Artifact |
|---|---|---|
| Planning | Athena | PLAN-<feature>.md |
| Implementation | Worker | IMPL-phase<N>-<agent>.md |
| Review | Themis | REVIEW-<feature>.md |
| Discovery | Apollo | DISC-<topic>.md |
| Decision | Any → Mnemosyne | ADR-<topic>.md |
Zeus does NOT generate artifacts. He orchestrates agents that generate them.
Templates
PLAN
# PLAN-<feature>
**Date:** YYYY-MM-DD **Status:** Awaiting Approval
## Goal
[One sentence]
## Phases
1. Phase 1 — @hermes
2. Phase 2 — @aphrodite
## Risks
- [Risk]
IMPL
# IMPL-<phase>-<agent>
**Date:** YYYY-MM-DD **Status:** Awaiting Themis Review
## What Was Implemented
- [file] — [what changed]
## Tests
- ✅ X tests / Coverage: Y%
REVIEW
# REVIEW-<feature>
**Status:** APPROVED | NEEDS_REVISION | FAILED
## Verdict
[APPROVED | NEEDS_REVISION | FAILED]
## Issues
- CRITICAL: X / HIGH: Y / MEDIUM: Z
Human Pause Points
- After PLAN → user reads
.tmp/PLAN-<feature>.mdand approves - After REVIEW → user reads
.tmp/REVIEW-<feature>.mdand validates focus items - Before git commit → user executes manually
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.
- 1mo ago First seen · 119 lines · 19 tokens per session scan A c60e493666be
artifact-management is a skill published in the GitHub repository ils15/pantheon-legacy (12 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 759 once invoked, about $0.0001 per session on Opus 5.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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.