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/vistyy/nopus/nopus-simplifynpx skills add Vistyy/nopus --skill nopus-simplifygit clone --depth 1 https://github.com/Vistyy/nopusWrote 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/vistyy/nopus/nopus-simplify)<a href="https://agentmods.dev/skills/vistyy/nopus/nopus-simplify"><img src="https://agentmods.dev/badge/skills/vistyy/nopus/nopus-simplify.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.00025 | $0.00155 |
| Opus 5 | $0.00013 | $0.00077 |
| Sonnet 5 | $0.00005 | $0.00031 |
| Haiku 4.5 | $0.00003 | $0.00015 |
Grade A, and why
nopus-simplify 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.
What it actually says
Simplify the previous response
Rewrite your immediately preceding completed response. If there is no preceding completed response, ask the user which text to rewrite.
Preserve its meaning and necessary detail. Preserve technical terms, identifiers, commands, paths, errors, quotations, constraints, conditions, causes, contrasts, and consequences. Do not shorten or summarize content when doing so would remove necessary information.
Use concrete subjects and actions where possible. Prefer familiar words when they are equally precise. Unpack dense phrases. Replace formulaic framing and filler with plain statements.
Return only the revised response.
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 · 22 lines · 25 tokens per session scan A 4acc5cddd58b
nopus-simplify is a skill published in the GitHub repository Vistyy/nopus (274 stars, last pushed 17d ago), licensed MIT. It adds 25 tokens to every session and 155 once invoked, about $0.0001 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
opensrc
Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…
context-efficient-coding
Use ContextFlux to minimize coding-agent context and tool calls when exploring, planning, debugging, reviewing, or modifying an unfamiliar or multi-file repository. Trigger for codebase discovery, symbol search, architecture questions, cross-file changes, error tracing, review feedback, test discovery, or any request…
minimize-token-usage
Reduce Codex context and token use while preserving evidence and correctness. Use for long coding, research, debugging, repository exploration, noisy logs, large command or MCP outputs, repeated file reads, cost-sensitive work, or when the user asks for concise, cheap, low-token, or context-efficient execution. Also…
trovex
Token-efficient routing for a repo's Markdown docs. Use BEFORE reading or grepping any .md file to find the one canonical doc for a question — and to read it at the section level instead of whole. Trovex serves the single current doc per query (with a canonical/stale/duplicate freshness marker) for 60% fewer tokens…
adaptive-token-efficiency
Escalation-only workflow for materially ambiguous, research-heavy, high-impact, cross-system, or failed-validation tasks. Do not load for clear, bounded, low-risk work; use the AGENTS fast path.
autonomous-loops
Patterns and architectures for autonomous Claude Code loops — from simple sequential pipelines to RFC-driven multi-agent DAG systems.