agentmods.dev

lint_wiki

lint_wiki is a skill for Claude Code, Codex from songzhuozhu/obsidian-llm-wiki. It costs 31 tokens per session (385 once invoked), scanned A, original, MIT.

A maintenance workflow for an inspool wiki, including its pages, sources, links, and unprocessed notes. It checks the wiki's structure, supporting evidence, relationships, and consistency.

In plain words
What is it for?
Use it to audit the wiki, identify low-risk content and structure problems, and fix issues such as missing relationships or inconsistent raw-material state.
Why use it?
It helps find orphaned or duplicate pages, unsupported claims, broken links between related ideas, stale raw notes, and mismatches between indexes and files.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

not rated 121repo 4mo ago A scan 31 tokens original MIT

Good fit Use it to audit the wiki, identify low-risk content and structure problems, and fix issues such as missing relationships or inconsistent raw-material state.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/songzhuozhu/obsidian-llm-wiki/lint_wiki
View source ↗ songzhuozhu/obsidian-llm-wiki
Install

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.

Any agent
npx skills add songzhuozhu/obsidian-llm-wiki --skill lint_wiki
Clone the repo
git clone --depth 1 https://github.com/songzhuozhu/obsidian-llm-wiki

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for lint_wiki

README.md
[![agentmods](https://agentmods.dev/badge/skills/songzhuozhu/obsidian-llm-wiki/lint_wiki/github.svg)](https://agentmods.dev/skills/songzhuozhu/obsidian-llm-wiki/lint_wiki)
Your own site
<a href="https://agentmods.dev/skills/songzhuozhu/obsidian-llm-wiki/lint_wiki"><img src="https://agentmods.dev/badge/skills/songzhuozhu/obsidian-llm-wiki/lint_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.

agentmods 80×15 button for lint_wiki

Your own site · 80×15
<a href="https://agentmods.dev/skills/songzhuozhu/obsidian-llm-wiki/lint_wiki"><img src="https://agentmods.dev/badge/skills/songzhuozhu/obsidian-llm-wiki/lint_wiki.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 385 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00385
Opus 5 $0.00015 $0.00192
Sonnet 5 $0.00006 $0.00077
Haiku 4.5 $0.00003 $0.00038

Measured 12d ago against content hash 4cbb18698b4c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

lint_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 12d 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.

.codex-en/skills/lint_wiki/SKILL.md · 40 lines

What it actually says

lint_wiki

Use this skill to run a structural and content-health audit across the entire wiki.

Steps

  1. Read inspool-wiki-en/AGENTS.md.
  2. Review inspool-wiki-en/wiki/index.md.
  3. Scan all page types under inspool-wiki-en/wiki/.
  4. Identify issues such as:
    • orphan pages
    • strong claims without source support
    • outdated conclusions invalidated by newer material
    • high-frequency concepts or entities that still lack their own pages
    • duplicate pages or inconsistent naming
    • clearly underlinked pages
    • knowledge pages that rely directly on external URLs instead of local source pages
    • missing supports, contradicts, or related_* fields on core pages
    • pages where relationships exist only in frontmatter but not in body links
    • source pages missing raw_note or external_url
    • stale raw/unprocessed/ strings left behind after approval
    • broken assumptions after user reclassification under concepts / entities / synthesis
    • mismatches between raw/index.md and the actual contents of raw/unprocessed/ and raw/processed/
    • raw material left in pending_review for too long
  5. Do not flag path strings that appear only as examples inside wiki/meta/; prioritize active leftovers in real source and knowledge pages.
  6. Produce a prioritized issue list.
  7. Fix low-risk structural issues directly when appropriate.
  8. Append the lint result to inspool-wiki-en/wiki/log.md.

Output Structure

  • findings
  • auto-fixed items
  • recommended next steps
Changes

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.

  1. 12d ago First seen · 40 lines · 31 tokens per session scan A 4cbb18698b4c

Subscribe to this mod's changes

lint_wiki is a skill published in the GitHub repository songzhuozhu/obsidian-llm-wiki (121 stars, last pushed 4mo ago), licensed MIT. It adds 31 tokens to every session and 385 once invoked, about $0.0002 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.

Writing and docs
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens