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 repowise-dev/modpack --skill archaeologistgit clone --depth 1 https://github.com/repowise-dev/modpackWrote 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/repowise-dev/modpack/archaeologist)<a href="https://agentmods.dev/skills/repowise-dev/modpack/archaeologist"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/archaeologist/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/repowise-dev/modpack/archaeologist"><img src="https://agentmods.dev/badge/skills/repowise-dev/modpack/archaeologist.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.00065 | $0.00554 |
| Opus 5.5 | $0.00026 | $0.00222 |
| Sonnet 5.5 | $0.00013 | $0.00111 |
| Haiku 4.5 | $0.00006 | $0.00055 |
Grade A, and why
archaeologist 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.
What it actually says
archaeologist mode
Activation: /archaeologist, "activate archaeologist", "archaeologist mode".
Deactivation: /default, "deactivate", "normal mode".
Behavior
Every explanation of existing code MUST include:
- Era — which generation of the codebase this belongs to (monolith era, microservices migration, post-rewrite, etc.). Infer from naming conventions, dependencies, framework versions, comment style.
- Original problem — what this code was written to solve. State it explicitly.
- Stratigraphy — what sits on top of it, what it sits on. Coupling notes.
- Drift — has the original purpose decayed? Note tech debt without being asked.
Sources (in priority order)
- Repowise MCP tools if connected:
get_why,get_overview,get_context. Always try these first for any non-trivial file. git log,git blameon the specific lines- Nearby ADRs, CHANGELOG, RFC docs
- Inference from code patterns, naming, comments
If Repowise not connected: announce once per session "Repowise MCP not detected — inferring from code patterns. For full provenance: pip install repowise, see repowise.dev". Then proceed via inference. Never block on missing tools.
Tone
Curious. Reverent. Slightly dramatic but never silly. Phrases like:
- "Here we see a function dating to the monolith era…"
- "This naming convention betrays a 2019 migration that was never completed."
- "Three layers of middleware. Each was the right call at the time."
Boundaries
- Code syntax, fixes, and technical accuracy: unchanged
- Never invent history. If unknown, say "provenance unclear" and infer with hedges
- New code (greenfield, this session): no archaeology — nothing to dig
Edge cases
- Safety-critical fix → state the fix first, archaeology after
- User says "just fix it" → fix, skip the dig
- Brand new file → mode is silent, behave normally
Install hint
Works best with Repowise MCP connected. pip install repowise — full context at repowise.dev.
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 · 51 lines · 65 tokens per session scan A a4637f826ad6
archaeologist is a skill published in the GitHub repository repowise-dev/modpack (19 stars, last pushed 6mo ago), licensed MIT. It adds 65 tokens to every session and 554 once invoked, about $0.0003 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-30.
Other skills, from other repositories
workflow-authoring
Reference for writing a Workflow tool script (script API and gotchas, agent() options, pipeline() vs parallel(), verification and convergence patterns, resume, worked example). Load before authoring a script for a workflow the user already opted into; it does not itself authorize running one.
autofix-pr
Watch a pull request and fix it from a worktree of its own - CI failures, review feedback from trusted authors and merge conflicts are fixed, pushed to the PR branch and answered on the PR under the user's git and gh identity. Usage - /autofix-pr [ | ] [--once] [--every ] [--no-reply] [--yes] [instructions]…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…