source-deep-dive

source-deep-dive is a skill for Claude Code, Codex from duc01226/EasyPlatform. It costs 41 tokens per session (3,137 once invoked), scanned A, original, MIT.

A research workflow that turns an earlier source map into a cited evidence document, recording where each finding came from and how certain it is.

In plain words
What is it for?
Use it for source-based research that needs traceable evidence, confidence notes, and explicit discrepancies.
Why use it?
It reduces the risk of treating an unverified claim or a disagreement between sources as fact.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions subagents; installed under .agents/ (shared by several agents).

Good fit Use it for source-based research that needs traceable evidence, confidence notes, and explicit discrepancies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/duc01226/easyplatform/source-deep-dive
Install

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.

Any agent
npx skills add duc01226/EasyPlatform --skill source-deep-dive
Clone the repo
git clone --depth 1 https://github.com/duc01226/EasyPlatform

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for source-deep-dive

README.md
[![agentmods](https://agentmods.dev/badge/skills/duc01226/easyplatform/source-deep-dive/github.svg)](https://agentmods.dev/skills/duc01226/easyplatform/source-deep-dive)
Your own site
<a href="https://agentmods.dev/skills/duc01226/easyplatform/source-deep-dive"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/source-deep-dive/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.

agentmods 80×15 button for source-deep-dive

Your own site · 80×15
<a href="https://agentmods.dev/skills/duc01226/easyplatform/source-deep-dive"><img src="https://agentmods.dev/badge/skills/duc01226/easyplatform/source-deep-dive.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,137 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00041 $0.03137
Opus 5.5 $0.00016 $0.01255
Sonnet 5.5 $0.00008 $0.00627
Haiku 4.5 $0.00004 $0.00314

Measured 3d ago against content hash a160959e7d17, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

source-deep-dive 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 3d 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.

.agents/skills/source-deep-dive/SKILL.md · 193 lines

How it starts

The opening of the file, as written. The whole thing — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Codex compatibility note:

  • Invoke $skill-name: load the registered .agents/skills/<name>/SKILL.md and execute it with Codex tools; no separate Skill tool or Claude mode switch is needed. Author .claude/**; mirrors are generated.
  • Track steps before execution and keep progress/evidence current. Explicit skill requests execute their protocol. Use the native question tool for required questions.
  • Map foreign tool names to available host capabilities. A name mismatch needs no approval; an actually unavailable required capability stops with its step/evidence and a user question before adaptation.
  • Subagent authorization: when a skill is user-invoked or AI-detected and its protocol requires subagents, that skill activation authorizes use of the required spawn_agent subagent(s) for that task.
  • Preserve protocol order unless the user approves a deviation. Workflows use $start-workflow: gates stay fixed; other steps may flex with logged reasons and evidence.

[BLOCKING MUST ATTENTION] Execute declared steps in order; NEVER skip, reorder, or merge without explicit user approval. [BLOCKING MUST ATTENTION] Update task tracking before/after each step or sub-skill: in_progress at start, completed at end. [BLOCKING MUST ATTENTION] Completed steps need brief evidence; skipped steps need explicit reason; if Task tools are unavailable, maintain an equivalent synchronized step tracker.

Quick Summary

Goal: Deep-dive the prior source map into a cross-validated, source-cited evidence base (tmp/research/_evidence-{slug}.md) where every finding has source trace and confidence, discrepancies stay explicit, and no unverified single-source claim becomes fact.

Summary:

  • Purpose/input: Consume prior tmp/research/_sources-{slug}.md; prioritize Tier 1-2, high-relevance, gap-covering sources; NEVER start a fresh search.
  • Ordered path: (1) load/prioritize source map → (2) fetch 5-8 sources with WebFetch (hard cap 8) → (3) extract claims, data, quotes, methodology, publication date, author credentials, source type → (4) cross-validate → (5) write evidence base.
  • Confidence gate: 2+ independent sources agree = high confidence; disagreement = both positions + discrepancy; one source = single source, unverified; declare 95/80/60/<60% for every finding.
  • Handoff/routes: Write tmp/research/_evidence-{slug}.md with inline citations, ## Unresolved Discrepancies, and ## Gaps Remaining; a direct run uses ask user question tool for the post-completion choice only (no routing question: a direct call is an explicit skill request).

Workflow:

  1. Read source map — Load tmp/research/_sources-{slug}.md; prioritize Tier 1-2, high relevance, and gap coverage.
  2. Fetch top sources — Run WebFetch for prioritized URLs; maximum 8 calls.
  3. Extract findings — Capture claims, data points, quotes, methodology, publication date, author credentials, and source type.
  4. Cross-validate — Compare findings; distinguish agreement, discrepancy, and unique-source claims; assign confidence.
  5. Build evidence base — Write structured findings, citations, confidence, discrepancies, and gaps to the output path.

Key Rules:

  • MUST ATTENTION Maximum 8 WebFetch calls per invocation; prioritize Tier 1-2 sources covering gaps.
  • MUST ATTENTION Every finding cites a specific source and confidence percentage; factual claims need 2+ independent sources.
  • MUST ATTENTION Conflicting claims → present both + flag discrepancy; one source → single source, unverified.
  • MUST ATTENTION Output the intermediate evidence base, not final synthesis; preserve discrepancy and gap sections.

Critical thinking: Be skeptical; apply critical/sequential thinking; trace every claim and state confidence (>80% to act).

Read the full file on GitHub · 193 lines

Changes

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.

  1. 3d ago First seen · 193 lines · 41 tokens per session scan A a160959e7d17

Subscribe to this mod's changes

source-deep-dive is a skill published in the GitHub repository duc01226/EasyPlatform (12 stars, last pushed yesterday), licensed MIT. It adds 41 tokens to every session and 3,137 once invoked, about $0.0002 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-10-18.

Related

Other skills, from other repositories

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens