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 letrplB/second-brain --skill no-surrendergit clone --depth 1 https://github.com/letrplB/second-brainWrote 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/letrplb/second-brain/no-surrender)<a href="https://agentmods.dev/skills/letrplb/second-brain/no-surrender"><img src="https://agentmods.dev/badge/skills/letrplb/second-brain/no-surrender/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/letrplb/second-brain/no-surrender"><img src="https://agentmods.dev/badge/skills/letrplb/second-brain/no-surrender.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.00047 | $0.02995 |
| Opus 5.5 | $0.00019 | $0.01198 |
| Sonnet 5.5 | $0.00009 | $0.00599 |
| Haiku 4.5 | $0.00005 | $0.00299 |
Grade A, and why
no-surrender 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 1mo 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/no-surrender
Intent. Test the user's mental grip on a claim. Write the result to the claim's engagement vector so the vault knows what the user has actually engaged with vs. what they've absorbed without verification. Read surrender-tracking-design.md at the repo root for the design rationale.
This verb is the architectural circuit-break for the calibration loop (model emits high confidence without reasoning; user accepts without verification). It is the only verb in the vault that writes engagement.
Gating — read every invocation, never cache
Step 1, always. Read vault/vault.yaml. Check surrender.enabled.
- If
surrender.enabledis missing,false, or anything other than literaltrue: print this and exit immediately:/no-surrender is gated by surrender.enabled in vault.yaml. Set surrender.enabled: true to enable. - Do not proceed. Do not write any file. Do not read any claim. The gate is the first action and the first thing to fail.
This is a behavioural gate (skill-instruction layer), not a runtime gate. The flag exists to make activation deliberate. Re-read on every invocation — never assume it's still on from a prior call.
Target forms
Single argument forms (mutually exclusive):
| Form | Example | Behaviour |
|---|---|---|
[[wikilink]] |
/no-surrender [[ai-tutor-design-must-embed...]] |
Resolve wikilink to file in notes/claims/ or notes/synthesis/; test that one claim |
| Path | /no-surrender notes/claims/some-claim.md |
Test that one claim |
_<topic-map> |
/no-surrender _ai-in-education |
Read MOC; sequentially test each claim under ## Core claims. User can /stop between claims. |
--weakest=N |
/no-surrender --weakest=5 |
Find N claims with lowest current effective engagement (after decay); test in order |
--recent-since=Nd |
/no-surrender --recent-since=14d |
Test claims with created date within last N days |
Optional modifier:
--axis=<name>— force a specific axis (mechanism,implications,falsifiability,bounds). Overrides default axis selection.
What ships with it
1 file 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.
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.
- 1mo ago First seen · 240 lines · 47 tokens per session scan A a5672db7e36d
no-surrender is a skill published in the GitHub repository letrplB/second-brain (1 stars, last pushed 5mo ago), licensed MIT. It adds 47 tokens to every session and 2,995 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
notebooklm-cli
Drives Google NotebookLM via the cli-web-notebooklm command-line tool — create and manage notebooks, add URL/text sources, ask questions grounded in the sources, and generate/download artifacts (audio overview, video, slide deck, mindmap, study guide, quiz, FAQ, briefing, infographic, data table). Use when the user…
explain
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do…
tutorial
Interactive walkthrough for new users. Learn by doing — each step creates real content in your vault. Three tracks (researcher, manager, personal) with a universal learning arc. Triggers on "/tutorial", "walk me through", "how do I use this".
learn
Research a topic and grow your knowledge graph. Uses Exa deep researcher, web search, or basic search to investigate topics, files results with full provenance, and chains to processing pipeline. Triggers on "/learn", "/learn [topic]", "research this", "find out about".
VaultForge
Process learning materials into structured Obsidian atomic notes with roadmaps, MOCs, and double-links. Auto-generate study vaults from PDFs, Markdown, Word, PowerPoint, and more with AI-powered note-taking, knowledge linking, and deep research. Supports English and Chinese output. Use when the user wants to build a…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.