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 Kshitijpalsinghtomar/depth-skills --skill ds-emergencegit clone --depth 1 https://github.com/Kshitijpalsinghtomar/depth-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/kshitijpalsinghtomar/depth-skills/ds-emergence)<a href="https://agentmods.dev/skills/kshitijpalsinghtomar/depth-skills/ds-emergence"><img src="https://agentmods.dev/badge/skills/kshitijpalsinghtomar/depth-skills/ds-emergence/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/kshitijpalsinghtomar/depth-skills/ds-emergence"><img src="https://agentmods.dev/badge/skills/kshitijpalsinghtomar/depth-skills/ds-emergence.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.00044 | $0.04666 |
| Opus 5.5 | $0.00018 | $0.01866 |
| Sonnet 5.5 | $0.00009 | $0.00933 |
| Haiku 4.5 | $0.00004 | $0.00467 |
Grade A, and why
emergence 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 25d 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 — 554 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EMERGENCE v2.0 — Interaction-Level Analyzer (Premium)
Mathematical Compliance: This skill implements the DEPTH-MATHEMATICS specification. It computes and outputs ADS phase activation, CEI components, SI components, cognitive traces (emergence risk quantification, interaction topology ), and verifies Gates V3, V4, V6. It quantifies emergence risk as a measurable metric.
You've analyzed each component. Each one is correct in isolation. Each passes its tests.
Now: what happens when they interact?
Emergence is what systems do that no individual part was designed to do. It is the traffic jam no car intended. The cascading failure no single service caused. The security vulnerability living in the gap between two correct components.
Component-level analysis cannot see this. These behaviors exist only in the interaction.
New in v2.0: Mathematical depth metrics, emergence risk quantification, interaction topology , recursive self-audit, verification gates.
The Failure Mode You Must Recognize
You just reviewed each component separately and declared them all correct. You are about to say "the system should work" without checking:
- Whether component A and component B both write to the same resource (contention)
- Whether component A's error handling triggers component B's error handling (feedback loop)
- Whether component A assumes it's the only consumer of a resource that component C also uses (assumption collision)
- Whether the behavior changes when component A responds in 5000ms instead of 50ms (timing dependency)
Individual correctness does not guarantee system correctness.
Cargo cult emergence lists components without quantifying interaction risk. This skill rejects it.
The Protocol
0 — PARAMETERIZE: Read Thinking Parameters
Read thinking_parameters:
min_components(default 3) — minimum components to analyzemin_hidden_interactions(default 2) — minimum hidden interactions to findrequire_risk_quantification(default true) — compute emergence risk quantificationrequire_topology_(default true) — issue interaction topologyrecursion_depth(default 1) — recursive self-audit rounds
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.
- 25d ago Changed · +365 lines · +18 tokens per session 940ad86d3566
- 1mo ago First seen · 189 lines · 26 tokens per session scan A 63b6d6c63d79
emergence is a skill published in the GitHub repository Kshitijpalsinghtomar/depth-skills (5 stars, last pushed 14d ago), licensed MIT. It adds 44 tokens to every session and 4,666 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-08-31.
Other skills, from other repositories
verification-quality
Truth scoring, code-quality verification, and automatic rollback with a high accuracy threshold. Use when validating agent output before it ships, gating changes on quality, or adding a verify-and-rollback safety loop.
refactoring-patterns
Code refactoring patterns with before/after diffs for extract method, extract class, inline, move, rename, dead code removal, dependency injection, and code smell detection.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
Verification & Quality Assurance
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
squid-architecture-review
Periodic architectural sweep — reads existing ADRs, maps modules/dependencies/layering, and reports up to 10 prioritised findings shaped as refactor proposals /squid-refactor can consume directly.
analyze
Analyzes code quality, complexity, patterns across codebase. Triggers: quality report, hotspot scan, code analysis, architecture signal.