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/epicsagas/epic-harness/reflectnpx skills add epicsagas/epic-harness --skill reflectgit clone --depth 1 https://github.com/epicsagas/epic-harnessWrote 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/epicsagas/epic-harness/reflect)<a href="https://agentmods.dev/skills/epicsagas/epic-harness/reflect"><img src="https://agentmods.dev/badge/skills/epicsagas/epic-harness/reflect.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.1 | $0.00026 | $0.02226 |
| Opus 5 | $0.00013 | $0.01113 |
| Sonnet 5 | $0.00005 | $0.00445 |
| Haiku 4.5 | $0.00003 | $0.00223 |
Grade A, and why
reflect 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 6d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reflect — Human AI-Usage Self-Assessment
This skill is for you (the human) to reflect on how well you're leveraging AI as a thought amplifier — not a review of agent performance.
Data source: The reflect hook (session-end) automatically collects observations, analyzes patterns, and updates metrics.json. This skill consumes that hook-produced data to produce a human-readable self-assessment.
Hook (auto) Skill (on-demand /reflect)
───────────── ──────────────────────────
observe → obs/*.jsonl ──→ epic reflect --context 30
evolve → metrics.json ──→ 5-dimension scorecard
seed → evolved skills ──→ Action items for the human
ingest → memory graph ──→ Trend analysis
Iron Law
No score without evidence. Every rating must directly cite at least one of: obs stats, evolution patterns, memory nodes, or session summaries. Block self-serving bias: "doing well" conclusions require concrete metrics.
Process
Step 0 — Collect Context
# Uses Rust subcommand — works on all platforms (Linux, macOS, Windows)
epic reflect --context 30 > /tmp/reflect_ctx.json
Fallback if subcommand fails:
echo "obs_files: $(ls "$HARNESS_DIR/obs/" | wc -l)"
python3 -c "import json; m=json.load(open('$HARNESS_DIR/metrics.json')); print('total_sessions:', m.get('total_sessions',0))"
Query memory (if active):
epic mem recall "AI usage patterns decisions metacognition" --limit 8
epic mem list --type decision --limit 5
epic mem list --type pattern --limit 5
Step 1 — 5-Dimension Reflection
Score each dimension independently: 1–10 + evidence citation + one-line diagnosis.
Dimension 1: Thought Amplification
Question: Is AI a mere executor (code typist) or a genuine thought partner?
Metrics:
- Agent tool call ratio (
Agent / total_obs— higher = delegated thinking) - Skill invocation frequency (meta-layer usage)
- council/discover/spec execution history
- Memory decision node count
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.
- 6d ago First seen · 221 lines · 26 tokens per session scan A ed5d32fc48a3
reflect is a skill published in the GitHub repository epicsagas/epic-harness (18 stars, last pushed yesterday), licensed Apache-2.0. It adds 26 tokens to every session and 2,226 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-30.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.