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 agentmods add skills/gideondk/strata/lintnpx skills add gideondk/strata --skill lintgit clone --depth 1 https://github.com/gideondk/strataWrote 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/gideondk/strata/lint)<a href="https://agentmods.dev/skills/gideondk/strata/lint"><img src="https://agentmods.dev/badge/skills/gideondk/strata/lint.svg" alt="Measured on agentmods" 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 | $0.00103 | $0.00919 |
| Opus 5 | $0.00051 | $0.00460 |
| Sonnet 5 | $0.00021 | $0.00184 |
| Haiku 4.5 | $0.00010 | $0.00092 |
Grade A, and why
strata: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 5d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
strata:lint
Pluggable scanner. Patterns live in presets/*.json, credentials by
Default, PII and region-specific PHI as opt-in presets. Add your own.
Even though the vault lives outside the repo and isn't usually committed, it is sync'd to other team members, same blast radius. Lint before sync.
When to use
- Periodically across the whole vault (
--scope vault, the default). - Before committing if you're export-promoting a decision into the host repo
(
--scope staged). - As part of a
pre-pushgit hook in the host repo (recommended — seeINSTALL.md).
How
The front door handles the venv automatically, invoke via
${CLAUDE_PLUGIN_ROOT}/bin/strata:
# Default: scan the whole vault with the `secrets` preset
"${CLAUDE_PLUGIN_ROOT}/bin/strata" lint
# Add region-specific PHI presets
"${CLAUDE_PLUGIN_ROOT}/bin/strata" lint \
--preset secrets,pii,phi-us
# Staged *.md files in the host repo
"${CLAUDE_PLUGIN_ROOT}/bin/strata" lint \
--scope staged --preset secrets,pii
# A specific file or directory
"${CLAUDE_PLUGIN_ROOT}/bin/strata" lint \
--scope ~/StrataVault/myrepo/pr-context/feat-x/
# Treat warnings as errors (CI mode)
"${CLAUDE_PLUGIN_ROOT}/bin/strata" lint \
--scope vault --preset secrets,pii --strict
Exit code 0 = clean, 1 = findings, 2 = misuse.
Bundled presets
| Preset | Catches |
|---|---|
secrets (default) |
AWS, GitHub, Slack, OpenAI, Anthropic tokens, JWTs, PEM blocks, connection-string passwords, Azure account keys, GCP service-account markers |
pii |
Credit cards (Luhn-validated), client/user-id literal assignments, emails |
phi-uk |
NHS numbers (Mod-11 verified), UK postcodes (BS7666) |
phi-us |
SSN (with structural validation), DEA numbers (checksum-verified) |
All findings are BLOCK-level by default, they detect actual identifier values, not vocabulary. The lint deliberately does not warn on words Like "SSN", "NHS number", or "HIPAA" appearing in prose, because team memory Notes will legitimately discuss systems that handle that data ("the SSN flow Goes through service X", "we don't store NHS numbers in this table"). That's the whole point of ADRs.
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.
- 5d ago First seen · 93 lines · 103 tokens per session scan A 43ca82c69753
strata:lint is a skill published in the GitHub repository gideondk/strata (5 stars, last pushed 1mo ago), licensed MPL-2.0. It adds 103 tokens to every session and 919 once invoked, about $0.0005 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
my-wiki
Manage local OKF-compatible Markdown My Wiki vaults with an AI agent. Use for capturing webpages, PDFs, Office documents, notes, images, folders, and ZIP bundles as References; maintaining Reference-to-Concept evidence links; searching or answering from a vault; checking or repairing vault health; switching among…
phase-orchestrator
Orchestrates phase-based implementation plans using the host's todo tracker and subagents for implementation, review, validation, default phase commits, plan finalization, and a final end-to-end review. Delegates work through the companion phase-implementer, phase-reviewer, and phase-final-reviewer skills and consumes…
save-to-favorites
The single complete Pickoo workflow for new Xiaohongshu, WeChat, Douyin, Bilibili, Xiaoyuzhou, podcast, music, article/blog, or general web links. Use for 收藏、保存、收录、抓取、归档、拆解、分析、OCR、ASR or 完整处理 from Codex, WorkBuddy, Hermes, Claude, or Claudian. It owns intake and the complete downstream workflow; obsolete standalone…
asset-review-agent
Independently review source-extracted quote, viewpoint, hook, and structure candidates. Image and shot assets are outside automatic review and enter only after explicit user interaction.
answer-processing
Use whenever the user uploads a hand-written or scanned answer PDF to be graded against a reference solution. Converts answer PDFs in answers/.pdf to markdown in answers/converted/.md using the pdf skill (OCR as needed), then performs strategy-based grading against converted/solutions/.md or quizzes/answers.md.…
course-builder
Use whenever the user wants to ingest a new course's materials (lecture notes, textbook chapters, HW problems, HW solutions) and build the course-specific knowledge base — patterns.md (recurring solution techniques), coverage.md (HW-to-section map with 🔥 exam tiers + ⚠weak flags), and summary.md (topic tree). Invoked…