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.
git clone --depth 1 https://github.com/jamditis/claude-skills-journalismWrote 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/plugins/jamditis/claude-skills-journalism/okf-wiki)<a href="https://agentmods.dev/plugins/jamditis/claude-skills-journalism/okf-wiki"><img src="https://agentmods.dev/badge/plugins/jamditis/claude-skills-journalism/okf-wiki.svg" alt="Measured on agentmods" height="20"></a>Grade A, and why
okf-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 8d 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.
What it actually says
{
"name": "okf-wiki",
"version": "0.8.3",
"description": "Scaffold an Open Knowledge Format (OKF) knowledge base from docs, plans, notes, or a repo: one-concept-per-file Markdown with YAML frontmatter, navigation, and validation. Built for newsroom memory, research atlases, decision logs, and infrastructure maps.",
"author": {
"name": "Joe Amditis",
"email": "[email protected]"
}
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 35 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 8d ago First seen · 10 lines scan A 8b1754e85155
okf-wiki is a plugin published in the GitHub repository jamditis/claude-skills-journalism (387 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
paper-discourse-graph
Audit LaTeX papers as discourse graphs for reader-state continuity, paragraph flow, planted/payoff questions, detours, and figure/equation placement.
tikz-figure-review
Review and fix alignment, label collision, clipping, legend-over-data, and overlap issues in TikZ and pgfplots figures inside LaTeX documents.
quarto
Collection of skills for Quarto document creation.
knowledge-and-memory
Research methodology, corpus search, persistent memory, iterative workflows, and project knowledge management.
rigorous-paper-reviewer
Deep 7-pass technical review of LaTeX papers — structure, notation, theorem/proof, numerics, complexity, figures, coherence. Includes a static Python verifier for automated triage of labels, cross-references, and structure.
ash-workflow
A plugin containing a Chinese product-planning workflow: writing product requirement documents, syncing them to Feishu, turning them into user stories, and preparing release announcements. Feishu is a collaboration and document platform.