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/tanya-ok/engineering-osWrote 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/tanya-ok/engineering-os/standards)<a href="https://agentmods.dev/plugins/tanya-ok/engineering-os/standards"><img src="https://agentmods.dev/badge/plugins/tanya-ok/engineering-os/standards/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/plugins/tanya-ok/engineering-os/standards"><img src="https://agentmods.dev/badge/plugins/tanya-ok/engineering-os/standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
engineering-os 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 3d 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": "engineering-os",
"version": "0.1.0",
"description": "Governance layer for engineering-os: canonical policies, skills, and lifecycle hooks for an infrastructure engineer's AI working environment",
"author": "engineering-os contributors",
"license": "MIT",
"homepage": "https://github.com/tanya-ok/engineering-os",
"repository": "https://github.com/tanya-ok/engineering-os",
"keywords": [
"obsidian",
"claude-code",
"rag",
"infrastructure",
"developer-tools"
]
}
What it installs
The manifest is a name and a version. 4 skills travel with it, and installing the plugin installs all of them — 235 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed da807b29da6c
- 1mo ago First seen · 17 lines scan A 6f1bb35a5636
engineering-os is a plugin published in the GitHub repository tanya-ok/engineering-os (2 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-31.
Other plugins, from other repositories
obsidian-wiki
Grow an Obsidian second brain with your AI agent: ingest docs, chat history and URLs into interlinked markdown, then query it with citations. Karpathy's LLM Wiki pattern as Claude Code skills.
obsidian-mcp-server
Read, write, search, and surgically edit Obsidian vault notes, tags, and frontmatter via MCP. STDIO or Streamable HTTP.
llm-wiki
Self-maintaining LLM wiki (Karpathy pattern): recall, observe, retro, capture sources, ensure pages, lint, and ingest. 15 tools over MCP.
journal
Personal journaling system built on Binder — morning briefings, day planning, reflections, summaries, and period-level goal tracking.
para-knowledge-base
Build, query, index, and audit portable PARA knowledge bases in Obsidian with privacy-safe operation telemetry.
kb
Build and maintain LLM-powered knowledge bases as Obsidian wikis with compile, query, lint, and evolve workflows.