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 nobrainer-tech/nobrainer-tech-skills --skill nobrainer-wikigit clone --depth 1 https://github.com/nobrainer-tech/nobrainer-tech-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/nobrainer-tech/nobrainer-tech-skills/nobrainer-wiki)<a href="https://agentmods.dev/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-wiki"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-wiki/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/nobrainer-tech/nobrainer-tech-skills/nobrainer-wiki"><img src="https://agentmods.dev/badge/skills/nobrainer-tech/nobrainer-tech-skills/nobrainer-wiki.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.00065 | $0.01612 |
| Opus 5 | $0.00032 | $0.00806 |
| Sonnet 5 | $0.00013 | $0.00322 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
nobrainer-wiki 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NoBrainer Wiki
Build and use a small, trustworthy knowledge system only when information should compound across tasks. This skill is explicitly inspired by Andrej Karpathy's LLM wiki concept and is an independent portable adaptation, not an official Karpathy project.
Read references/setup.md before creating or reconnecting a wiki. One skill owns all wiki behavior so setup, query, capture and maintenance cannot drift into competing wrappers.
Select one mode
SETUP: decide whether a wiki is justified, then create/connect/govern it.GET: read-only targeted retrieval. This is the default for a question.ADD: explicit ingestion or promotion of durable knowledge.TIDY_AUDIT: inspect trust, links, freshness and backlog without writing.TIDY_APPLY: apply only deterministic approved maintenance after an audit.
Do not combine modes invisibly. A GET that discovers a durable insight does
not authorize ADD; a tidy audit does not authorize semantic rewrites.
Decide whether a wiki is justified
Prefer normal repository documentation when knowledge is local to one codebase and already discoverable. A wiki is justified when durable decisions, sources, research, explicit owner preferences or operational knowledge must be queried across tasks/sessions and would otherwise be repeatedly reconstructed.
Do not store live execution state, leases, current hashes, transient blockers, credentials or secrets. A spec defines a contract; a plan orders work; a wiki preserves reusable knowledge. One fact has one canonical owner.
Shared safety and knowledge contract
Resolve the wiki root from project instructions or the owner; never guess a destination. Read its rules, index, classification boundary, relevant pages and dirty/writer state before any operation.
Classify source and destination:
PUBLIC: safe for intentional disclosure;INTERNAL: non-public operating knowledge without restricted personal data;CONFIDENTIAL: explicitly restricted, minimum necessary content;SECRET: credentials, keys, tokens, cookies, seed phrases or equivalents.
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.
- 11d ago First seen · 157 lines · 65 tokens per session scan A 925bb17109df
nobrainer-wiki is a skill published in the GitHub repository nobrainer-tech/nobrainer-tech-skills (5 stars, last pushed 6d ago), licensed MIT. It adds 65 tokens to every session and 1,612 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
doc-drift
Use this skill when the user wants to audit the memory and documents Claude Code loads into context — CLAUDE.md (user global + project + nested), MEMORY.md, @imports, .claude/skills, .claude/agents, .claude/commands, installed plugins — and detect four kinds of issues: outdated claims, mutually contradictory…
session-checkpoint
Use when saving session state before context compaction, switching tasks, or ending a session. Runs 5-phase pipeline: context extraction → handoff write → memory save → preservation check → compact guidance.
conversation-council
A conversation tool that brings selected past chats into a new discussion as separate first-person advisers. It supports Reasonix and Codex session formats.
ciel
Autonomous partner intelligence and master cognitive orchestration layer for software engineering, deep research, AAA+ 3D spatial modeling, and multi-agent coordination. Use when orchestrating complex workflows, architecting multi-domain systems, routing tasks through specialized specialist guilds, conducting rigorous…
multi-agent-loop
Turn the current repository into a supervised multi-agent coding loop — spawn parallel AI coding agents in isolated git worktrees with file ownership, a shared radar, and human approval gates, then run the loop (status, standup, approvals) from one place.
openakashic
Persistent memory for AI agents across sessions. Search what others figured out, write what you learn, publish what deserves a wider audience.