Borrowing it
Nothing to install: this file belongs to Gixsy95/abap_wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Gixsy95/abap_wiki/main/.agents/skills/lint-audit/SKILL.mdgit clone --depth 1 https://github.com/Gixsy95/abap_wikiWrote 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/gixsy95/abap_wiki/lint-audit)<a href="https://agentmods.dev/skills/gixsy95/abap_wiki/lint-audit"><img src="https://agentmods.dev/badge/skills/gixsy95/abap_wiki/lint-audit/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/gixsy95/abap_wiki/lint-audit"><img src="https://agentmods.dev/badge/skills/gixsy95/abap_wiki/lint-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00078 | $0.00588 |
| Opus 5 | $0.00039 | $0.00294 |
| Sonnet 5 | $0.00016 | $0.00118 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
lint-audit 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 10d 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lint & audit - knowledge base integrity
Verifies the consistency of the vault and the state. Deterministic fixes are allowed; deleting pages or downgrading doc_level is not (never without an explicit request).
Commands
-
Vault lint (frontmatter, wikilinks, citations, nested tags, wiki<->DB drift):
python core/src/tools/lint_wiki.pyReport in
output/reports/lint-report.md. Exit code 1 if there are issues. -
Agent contract synchronization (.claude/agents/ must match the canonicals):
python core/src/tools/sync_agents.py --checkIf drift is found, regenerate with
python core/src/tools/sync_agents.py. -
Progress dashboard (view regenerated from DB):
python core/src/tools/pipeline.py dashboardGenerates
output/reports/pipeline-dashboard.md.
What the lint checks
- Frontmatter: every page is parsed via
yaml.safe_load(a broken frontmatter is a blocking issue). - Wikilinks: every
[[slug]]points to an existing page. - Citations: every
[VERIFIED: <path>:N-M]resolves to a real file within EOF, from a citable root (raw/,slices/). The analysis is inline in the object page (§2): there is no longer a separate citableabap_wiki/analysis/tree. - Nested tags: confidence markers cannot contain other tags/wikilinks.
- Wiki<->DB drift: comparison between page slugs and DB rows.
Tracking (operational log)
lint_wiki.pyautomatically records alintevent (issues/pages) in theeventstable: it appears inlog.md(the append-only view) at the nextgit-commitorpipeline.py log. No manual action needed.- A manual fix made outside the pipeline must be recorded explicitly:
pipeline.py log-op --type meta --note "<what you fixed>" [--object <id>].
Prohibitions
- Never delete pages, lower
doc_level, or modifyraw/without an explicit request. - Never mark a source
unavailablewithout evidence. - "User notes" sections are hard-protected: never overwritten.
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.
- 10d ago First seen · 51 lines · 78 tokens per session scan A 2f16461a4f86
lint-audit is a skill published in the GitHub repository Gixsy95/abap_wiki (44 stars, last pushed 2d ago), licensed MIT. It adds 78 tokens to every session and 588 once invoked, about $0.0004 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
link-health
Use at the start of Link work when readiness is unclear, after installs or upgrades, and before repairs; verify health, inspect interrupted writes, back up, and repair generated indexes without MCP.
status
Verify gnosis-mcp server connectivity, schema integrity, and corpus health. Use when MCP calls fail, return empty, or return unexpected data.
neuron-debugger
Debug and monitor Neuron AI applications with Inspector APM, event observability, logging, and performance analysis. Use this skill whenever the user mentions debugging, monitoring, observability, performance analysis, tracing, Inspector, or needs to understand why an agent is behaving a certain way. Also trigger for…
agent-identity
Verify an agent's live address and billing account before sharing a chat link, diagnosing a deploy mismatch, or deciding why two hosts share an identity.
data-fetching
Use when implementing or debugging ANY network request, API call, or data fetching. Covers fetch API, axios, React Query, SWR, error handling, caching strategies, offline support.
link-memory
Use after important user-approved decisions, when durable context should be proposed or reviewed, and for explicit Link memory lifecycle work: remember, recall, review, update, archive, restore, forget, or explain local memories through the CLI without requiring MCP.