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/tanya-ok/engineering-os/clone-projectsnpx skills add tanya-ok/engineering-os --skill clone-projectsgit 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/skills/tanya-ok/engineering-os/clone-projects)<a href="https://agentmods.dev/skills/tanya-ok/engineering-os/clone-projects"><img src="https://agentmods.dev/badge/skills/tanya-ok/engineering-os/clone-projects.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.00053 | $0.00628 |
| Opus 5 | $0.00026 | $0.00314 |
| Sonnet 5 | $0.00011 | $0.00126 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
clone-projects 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 4d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
clone-projects
engineering-os holds your knowledge (the vaults) and, with this skill, the
actual code too. It clones the repositories listed in a manifest into a
workspace organized by the same five domains as the work vault, so
workspace/CloudOps/ mirrors vault-template/CloudOps/: a runbook and the
stack it documents live one directory apart.
Manifest
Copy projects.example.tsv to projects.tsv at the repo root and list your
repos. It is tab-separated, the header row is skipped:
repo domain subcategory
network-stack CloudOps _
cost-reports FinOps _
ci-pipelines DevOps tooling
- repo - the repository name (the org is supplied separately).
- domain - any top-level folder; use the five vault domains (CloudOps, FinOps, DevOps, SecOps, Architecture) to keep code and notes aligned.
- subcategory - an optional extra nesting level;
_or empty means none.
projects.tsv is gitignored; it is your data, not part of the kit.
Run
export EOS_GITHUB_ORG=your-org # required: the GitHub org or owner
# optional: EOS_WORKSPACE_PATH=~/work # default is a sibling engineering-os-workspace
./standards/skills/clone-projects/clone-projects.sh # clone what is missing
./standards/skills/clone-projects/clone-projects.sh --sync # also fetch --prune existing clones
The script is idempotent: existing clones are skipped (or fetched with
--sync), so it is safe to re-run. It uses gh if available (handles private
repos and auth), otherwise git clone over HTTPS. Every action is logged to
clone.log in the workspace, and it exits non-zero if any repo failed.
Layout produced
engineering-os-workspace/ (sibling of the engineering-os repo)
CloudOps/
network-stack/ <- git clone
observability/monitoring/ <- domain/subcategory/repo
FinOps/
cost-reports/
DevOps/
tooling/ci-pipelines/
Why this shape
The workspace is a derived, disposable checkout of remote repos: delete it and re-run to rebuild. Keeping it a sibling of the engineering-os repo (not nested inside) keeps the kit small and avoids committing other people's code. Mirroring the vault domains means an agent that searched the vault for a CloudOps runbook can find the matching code in the same domain folder.
What ships with it
1 file beside SKILL.md 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.
- 4d ago First seen · 68 lines · 53 tokens per session scan A 3601fa116ff7
clone-projects is a skill published in the GitHub repository tanya-ok/engineering-os (2 stars, last pushed 11d ago), licensed MIT. It adds 53 tokens to every session and 628 once invoked, about $0.0003 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
llm-wiki
The foundational knowledge distillation pattern for building and maintaining an AI-powered Obsidian wiki. Based on Andrej Karpathy's LLM Wiki architecture. Use this skill whenever the user wants to understand the wiki pattern, set up a new knowledge base, or needs guidance on the three-layer architecture (raw sources…
wiki-lint
Audit and maintain the health of the Obsidian wiki. Use this skill when the user wants to check their wiki for issues, find orphaned pages, detect contradictions, identify stale content, fix broken wikilinks, or perform general maintenance on their knowledge base. Also triggers on "clean up the wiki", "what needs…
wiki-status
Show the current state of the wiki — what's been ingested, what's pending, and the delta between sources and wiki content. Use this skill when the user asks "what's the status", "how much is ingested", "what's left to process", "show me the delta", "what changed since last ingest", "wiki dashboard", or wants an…
wiki-dashboard
Create dynamic, queryable dashboard views of the Obsidian vault using Obsidian Bases or Dataview. Use this skill when the user says "create a dashboard", "vault dashboard", "show all X as a table", "dynamic view", "query my vault", "build a content index", "show me all concepts/entities/projects", or wants a…
wiki-import
Import a wiki knowledge graph into the current vault — either from a graph.json export file (stubs) or from an OKF (Open Knowledge Format) markdown bundle (full page bodies). Use this skill when the user says "import wiki", "import from export", "load graph.json", "import vault", "import OKF bundle", "import OKF"…
wiki-research
Autonomously research a topic via multi-round web search, synthesize findings, and file structured results into the Obsidian wiki. Use this skill when the user says "/wiki-research [topic]", "research X", "find everything about Y", "do a deep dive on Z", "autonomous research on X", or wants comprehensive, web-sourced…