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 skills add shalintripathi/organic-os --skill resetgit clone --depth 1 https://github.com/shalintripathi/organic-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/shalintripathi/organic-os/reset)<a href="https://agentmods.dev/skills/shalintripathi/organic-os/reset"><img src="https://agentmods.dev/badge/skills/shalintripathi/organic-os/reset/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/shalintripathi/organic-os/reset"><img src="https://agentmods.dev/badge/skills/shalintripathi/organic-os/reset.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00080 | $0.00947 |
| Opus 5 | $0.00040 | $0.00474 |
| Sonnet 5 | $0.00016 | $0.00189 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade C, and why
reset scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
remove it themselves: `rm -rf <brain-path>` for the local copy, plus How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
organic-os reset (guided teardown)
organic-os never deletes anything irreversible automatically. This skill walks the user through everything that exists for a site and what to do about each piece, then only touches the local registry with explicit confirmation.
Step 1: show what exists
- Read
~/.config/organic-os/sites.yamlviacore.registry.load(): list every registered site (slug, name, url, brain path) and which one is active. - List files in
~/.config/organic-os/- the per-site env files (<slug>.env, holdingWP_APP_PASSWORD/TELEGRAM_BOT_TOKEN) and the registry file itself. - For the site the user is asking about: report whether its brain path exists on disk and whether it is a git repo (has a remote or not).
Step 2: ask which site to tear down
AskUserQuestion: which registered site (or "all"). Confirm before any write.
Step 3: walk through each piece, per site
Only items 2 and 6 below are things this skill performs, each only with explicit confirmation. Everything else is the user's own action - state why for each.
- Scheduled routines: point at the runtime's own mechanism. If runtime
mode is
claude-scheduled, tell the user to remove the scheduled task from their Claude scheduler. Ifci, tell them to disable/delete the workflow file or cron entry in their CI system. organic-os does not manage the runtime's own scheduler and cannot deregister a routine for them. - Registry entry: with explicit confirmation, remove the site from
~/.config/organic-os/sites.yamlby callingcore.registry.unregister(<slug>). If the removed site was active, tell the user no site is active until they register or switch to another one. - Brain repo: organic-os never deletes it, on this skill's own authority
or the user's request in this session. It is the site's memory - signals,
decisions, reflections, skillbook, outcomes - and often has git history the
user wants to keep or archive. Tell the user the exact path and how to
remove it themselves:
rm -rf <brain-path>for the local copy, plus deleting the remote repo from GitHub/GitLab settings if it was pushed. - WordPress Application Password: organic-os cannot revoke it. Tell the user: WP Admin > Users > Profile > Application Passwords, revoke the one created for organic-os.
- Telegram bot token: if the approval channel was telegram, tell the
user they can revoke/regenerate it via @BotFather's
/revokecommand if they want to fully cut access. Deleting the env file alone stops polling but does not invalidate the token. - Env file: with explicit confirmation, delete
~/.config/organic-os/<site-slug>.env.
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.
- 2d ago First seen · 79 lines · 80 tokens per session scan C f931d4a3f9a2
reset is a skill published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed 3d ago), licensed MIT. It adds 80 tokens to every session and 947 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-08.
Other skills, from other repositories
import-sop
Import agency Standard Operating Procedures — approval workflows, campaign launch checklists, escalation procedures, QA steps — and structure them into numbered, role-assigned steps with human-approval gates marked. SOPs save at the agency level so they apply across every client brand, not per-brand. Triggers on…
client-onboarding
Generate a complete onboarding package for a new marketing client — kickoff meeting agenda, 20-30 question discovery questionnaire, stakeholder map with RACI matrix, platform-by-platform access checklist, 30-60-90 day milestone plan, communication cadence, escalation protocol, welcome email template, internal team…
github-operations
GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.
seo-vertical-detect
Classify a website as ecommerce, local-business, blog-publisher, saas, docs, or generic (multiple may apply), and report detected locales, from the persisted PageSnapshot plus the platform detector's vertical hints. Used by seo-orchestrator to decide which conditional modules to run and how to reweight the scores.
seo-fix-apply
Writer protocol preloaded into the seo-fixer-writer agent — how confirmed SEO/AI-search fixes are applied (git pre-flight, backup, Edit/Write for local diffs, ticketed adapter CLIs for remote targets, re-verify, publish only on a second ticket, rollback) and the findings-array output contract. Used only by the fix…
audit
Audit a website or web codebase for SEO and AI-search (GEO/AEO) — produces two independent 0-100 scores (Search SEO + AI Visibility) plus a prioritized, evidence-backed report persisted on disk. Read-only; never writes to the project. Use when the user asks to audit, analyze, check, or score a site's SEO, structured…