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/curiositech/some_claude_skills/code-necromancernpx skills add curiositech/some_claude_skills --skill code-necromancergit clone --depth 1 https://github.com/curiositech/some_claude_skillsWrote 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/curiositech/some_claude_skills/code-necromancer)<a href="https://agentmods.dev/skills/curiositech/some_claude_skills/code-necromancer"><img src="https://agentmods.dev/badge/skills/curiositech/some_claude_skills/code-necromancer.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.00070 | $0.01475 |
| Opus 5 | $0.00035 | $0.00737 |
| Sonnet 5 | $0.00014 | $0.00295 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
code-necromancer 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Necromancer
Tagline: Raise dead codebases from the grave
Systematic framework for understanding, resurrecting, and modernizing legacy codebases.
When to Activate
✅ Use when:
- Inheriting a codebase with 5+ repos and no documentation
- Resurrecting a product dormant for 2+ years
- Joining a company with significant technical debt and tribal knowledge loss
- Performing due diligence on acquired codebases
- Modernizing legacy systems without breaking existing functionality
❌ NOT for:
- Greenfield projects (start fresh instead)
- Well-documented active codebases
- Simple bug fixes in maintained systems
The Three Phases
Phase 1: ARCHAEOLOGY
Objective: Create a complete map before touching anything.
| Output | Description |
|---|---|
repo-inventory.json |
All repos with metadata, languages, activity |
dependency-graph.mmd |
Inter-repo and external dependencies |
architecture-diagram.mmd |
Visual system topology |
tech-stack-matrix.md |
Language/framework versions per repo |
maturity-assessment.md |
Code quality, test coverage, docs quality |
missing-pieces.md |
Gaps, orphaned repos, broken integrations |
Process: Inventory → Deep Scan → Cross-Reference → Visualize → Assess
→ See references/archaeology-guide.md for detailed techniques.
Phase 2: RESURRECTION
Objective: Get the system running in development.
| Output | Description |
|---|---|
dependency-audit.md |
Outdated packages, vulnerabilities, breaking changes |
environment-variables.md |
All required env vars with defaults |
secrets-needed.md |
API keys, certs, OAuth credentials |
infrastructure-status.md |
Cloud resources, what exists vs deleted |
resurrection-blockers.md |
Critical issues preventing launch |
integration-tests/ |
Tests verifying components work and communicate |
Process: Audit Dependencies → Map Environment → Check Infrastructure → Write Tests → Document Blockers
What ships with it
11 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.
- CHANGELOG.md 1.1 KB
- references/archaeology-guide.md 7.3 KB
- references/dependency-patterns.md 5.4 KB
- references/framework-detection.md 5.9 KB
- references/infrastructure-mapping.md 5.7 KB
- references/integration-test-patterns.md 7.9 KB
- scripts/analyze-repo.sh 12 KB runs code
- scripts/scan-repos.sh 6.0 KB runs code
- templates/archaeology-report.md 6.2 KB
- templates/repo-inventory.json 2.6 KB
- templates/resurrection-plan.md 5.5 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.
- 6d ago First seen · 173 lines · 70 tokens per session scan A 7f9d8bca4638
code-necromancer is a skill published in the GitHub repository curiositech/some_claude_skills (211 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 1,475 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…