Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add shalintripathi/organic-os/plugin install 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/hoo-import-audit)<a href="https://agentmods.dev/skills/shalintripathi/organic-os/hoo-import-audit"><img src="https://agentmods.dev/badge/skills/shalintripathi/organic-os/hoo-import-audit/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/hoo-import-audit"><img src="https://agentmods.dev/badge/skills/shalintripathi/organic-os/hoo-import-audit.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.00050 | $0.00811 |
| Opus 5 | $0.00025 | $0.00405 |
| Sonnet 5 | $0.00010 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
hoo-import-audit 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 11d 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
Import an external audit (claude-seo shape)
Turns a point-in-time audit report into organic-os proposals without re-deriving the audit. The import trusts but attributes: findings keep their original evidence labels ([Measured]/[Inference]/[Unverified]), the original finding text rides in each proposal verbatim, and anything our own audit dimensions would dispute is flagged for the human, never silently rewritten.
- Input: a file path from the user (a FULL-AUDIT-REPORT.md, an ACTION-PLAN.md, or similar markdown) or report text pasted in chat. Pasted text: write it to a temp file first. Read site-profile.yaml for the approval channel and the site URL.
- Parse and rank with the import module - stdlib only, defensive by
design (the format is theirs and may vary between versions; whatever
matches no item pattern is preserved in
parsed["unparsed"], never dropped):PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -csnippet importinghoo.audit_import-parsed = parse_report(text), thenprops = to_proposals(parsed, max_items=5). - Create each proposal via
create_item(kind=p["kind"], slug=p["slug"], title=p["title"], body=p["body"], target=<the finding's page URL if one appears in it, else parsed["source_meta"]["page_url"], else the profile site URL>, source="import-audit").create_itemis the ONLY birth path - items are bornproposedwith an empty approvals list and are NEVER auto-approved; approval is the human's act, on the normal gate. Each body already carries the verbatim finding (quoted), its evidence label, the attribution line, and the dimension-mapping note: overlap names the onsite-audit dimension (skills/onsite-audit steps 3-4) via theDIMENSION_HINTSmap inplugin/lib/hoo/audit_import.py; an llms.txt finding gets the deliberate-skip note (our position in plugin/docs/evidence.md); no overlap is marked external-only and imported as-is on the source audit's evidence. - Present a summary table in-session:
- imported items: title, source severity, dimension mapping (dimension name | deliberate-skip | external-only)
- skipped items: title + reason (ranked below the max_items cut; re-run with a higher max_items to import them)
- unparsed excerpt count, with a pointer that the excerpts were preserved, not dropped
- Rebuild the queue and route the approval notification through the
configured channel exactly like any propose run: one
core.approval.notify_pending(<brain>, send)call with the channel selection from skills/onsite-propose step 4. An item is marked notified ONLY after its send returns without raising, so a failed send is retried on the next run rather than lost, and re-runs never re-notify. - Append ONE signal recording the import: source audit date
(
parsed["source_meta"]["audit_date"]), items parsed, proposals created, skipped count, unparsed excerpt count.
Pattern credit: claude-seo (https://github.com/AgriciDaniel/claude-seo), credited in README.md since v0.1.0. They audit, we operate.
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.
- 11d ago First seen · 59 lines · 50 tokens per session scan A 2207453d2d12
hoo-import-audit is a skill published in the GitHub repository shalintripathi/organic-os (5 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 811 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
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…
ai-visibility
Fast-path AI visibility — get a brand's 0–100 Akii Visibility Score (computed by an open-source LLM judge against the brand's public footprint) with four-dimension breakdown AND a per-engine proxy map for ChatGPT, Claude, Gemini, Perplexity, Copilot, and Google AI Overviews based on FirstPageSage signal weights.…
optimize-page
Comprehensive single-page optimization across all three layers — traditional SEO (title / meta / H1 / internal links), AEO (chunk quality, direct-answer leads, FAQ extraction), and GEO rewrites using the tactics published by the Princeton/IIT Delhi GEO study (citation integration, expert quotes, statistics enrichment…
seo-audit
Single audit entry point — surface-level scorecard or deep infrastructure dive depending on the requested mode. Default full mode produces a multi-layer scorecard across all 9 areas (crawlability, indexation, meta tags, headings, images, Core Web Vitals, JS rendering, mobile + security, structured data, internal…