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 ariadoss/superskills --skill negentropy-lensgit clone --depth 1 https://github.com/ariadoss/superskillsWrote 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/ariadoss/superskills/negentropy-lens)<a href="https://agentmods.dev/skills/ariadoss/superskills/negentropy-lens"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/negentropy-lens/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/ariadoss/superskills/negentropy-lens"><img src="https://agentmods.dev/badge/skills/ariadoss/superskills/negentropy-lens.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.00059 | $0.00558 |
| Opus 5 | $0.00030 | $0.00279 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
negentropy-lens 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 11d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Negentropy Lens
A decision-support framework for evaluating systems through two fundamental states.
Core Definitions
- Entropy: "the natural tendency of systems toward decay, disorder, and complexity without value"
- Negentropy: "the deliberate reversal of decay — growth, compounding value, increasing order"
- Tacit knowledge: "the unwritten, unspoken knowledge of how things actually work — assumptions, workarounds, and institutional memory"
Central principle: "Every system exists in one of two states. Every decision either accelerates entropy or drives negentropy. There is no neutral."
Five-Phase Decision Process
Phase 1: Map the System
- Define boundaries and components
- Identify information flows and interfaces
- Map connection points and dependencies
Phase 2: Diagnose the State
- Classify entropic decay vs. negentropic growth indicators
- Identify stability traps masquerading as health
- Rate the current trajectory
Phase 3: Surface Tacit Knowledge
- Probe for hidden assumptions
- Find undocumented workarounds
- Uncover institutional memory dependencies
- Ask: "What does the system actually do vs. what the docs say it does?"
Phase 4: Evaluate the Decision
- Assess entropy alignment
- Compounding potential (does this create more value over time?)
- Knowledge externalization (does this reduce tacit knowledge debt?)
- Reversibility (how hard to undo?)
Phase 5: Challenge Constructively
- Flag false progress (complexity disguised as improvement)
- Identify local optimization at global expense
- Challenge assumptions about what "growth" means
Key Warnings
Anti-Patterns
- Entropy cosplay: complexity disguised as progress — adding abstractions that solve no real problem
- Premature formalization: documenting tacit knowledge before understanding it fully
- Negentropy theater: refactoring for its own sake, no value created
- Symptom management: fixing surface issues without addressing root causes
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.
- 11d ago First seen · 72 lines · 59 tokens per session scan A 7904994a601a
negentropy-lens is a skill published in the GitHub repository ariadoss/superskills (9 stars, last pushed 4d ago), licensed MIT. It adds 59 tokens to every session and 558 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-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.