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 jessepinkman9900/claude-second-brain --skill lintgit clone --depth 1 https://github.com/jessepinkman9900/claude-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/jessepinkman9900/claude-second-brain/lint)<a href="https://agentmods.dev/skills/jessepinkman9900/claude-second-brain/lint"><img src="https://agentmods.dev/badge/skills/jessepinkman9900/claude-second-brain/lint/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/jessepinkman9900/claude-second-brain/lint"><img src="https://agentmods.dev/badge/skills/jessepinkman9900/claude-second-brain/lint.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.00062 | $0.00625 |
| Opus 5 | $0.00031 | $0.00313 |
| Sonnet 5 | $0.00012 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00063 |
Grade A, and why
lint 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 9d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint
Runs the full lint workflow defined in CLAUDE.md. Checks for six categories of issues, fixes what can be fixed automatically, and reports the rest.
Workflow
Run all six checks. For each: identify issues, apply fixes where possible, and note anything that needs user input.
Check 1 — Orphan pages
- Find wiki pages with no inbound
[[links]]from any other wiki page - Glob
wiki/*.md, read each, check whether any other page links to it - Fix: add links from relevant topic pages where appropriate
- If a page is a stub with no clear home, flag it for the user to decide
Check 2 — Unresolved contradictions
- Grep
wiki/for[!WARNING] Contradictioncallouts - Report each one: which pages, what the conflict is, which sources are involved
- Fix: flag to user with a recommendation — a new source may resolve it
Check 3 — Stale claims
- Look for claims on older pages that newer source-summary pages have superseded
- Cross-reference
updateddates in frontmatter against source dates - Fix: update the claim and update the
sourcesfrontmatter attribution
Check 4 — Missing pages
- Find
[[wikilinks]]that appear frequently across wiki pages but have no corresponding file - Glob
wiki/*.md, extract all[[...]]links, check each against the file system - Fix: create stub pages for high-frequency missing links and queue them for ingestion
Check 5 — Broken links
- Find
[[wikilinks]]pointing to files that don't exist - Fix: create the missing page as a stub, or correct the link if it's a typo
Check 6 — Data gaps
- Identify important topics in the wiki that have many cross-references but thin source coverage
- Look for topic pages with empty or sparse
sourcesfrontmatter - Report: suggest specific sources, articles, or web searches to fill each gap
Output
Produce a lint report with three sections:
- Issues found — count and description per category
- Fixes applied — what was changed automatically
- Next sources to investigate — recommended reads to address data gaps or resolve contradictions
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.
- 9d ago First seen · 58 lines · 62 tokens per session scan A a8a8dda3dda2
lint is a skill published in the GitHub repository jessepinkman9900/claude-second-brain (47 stars, last pushed 4mo ago), licensed MIT. It adds 62 tokens to every session and 625 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-30.
Other skills, from other repositories
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…
diagnose-backend-bug
Diagnose a bounded backend or multi-service failure from GitHub Issues, Jira, Aone, user-provided exports, logs, traces, responses, stack traces, or job records. Use when a service, API, RPC, worker, queue, CLI, or scheduled job bug needs correlation through the project's existing observability route before repair; do…
debug-live
Guides root-cause investigations with debugging capabilities by setting breakpoints, starting a debug session, stepping through execution, inspecting variables, and tracing symptoms back to their origin. Prefer it for runtime bugs, failing tests, exceptions, crashes, hangs, wrong/null values, and unexpected output…
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
karpathy-llm-wiki
Use when building or maintaining a personal LLM-powered knowledge base. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki quality, 'add to wiki', 'what do I know about', or any mention of 'LLM wiki' or 'Karpathy wiki'.