Octop is a self-hosted, multi-user AI assistant that runs multiple specialized agents and connects them to chat interfaces, tools, and external services. It is for individuals, families, and teams who want a locally operated assistant with shared experts and persistent capabilities. Catalogue add-ons extend its agent and assistant workflows.
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 TencentCloud/Octop --skill medical-source-failovergit clone --depth 1 https://github.com/TencentCloud/OctopWrote 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/tencentcloud/octop/medical-source-failover)<a href="https://agentmods.dev/skills/tencentcloud/octop/medical-source-failover"><img src="https://agentmods.dev/badge/skills/tencentcloud/octop/medical-source-failover/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/tencentcloud/octop/medical-source-failover"><img src="https://agentmods.dev/badge/skills/tencentcloud/octop/medical-source-failover.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00087 | $0.01389 |
| Opus 5 | $0.00044 | $0.00694 |
| Sonnet 5 | $0.00017 | $0.00278 |
| Haiku 4.5 | $0.00009 | $0.00139 |
Grade A, and why
medical-source-failover 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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Medical Source Failover
Retrieve the intended medical document reliably without laundering a secondary source into primary evidence.
Non-negotiable invariant
Degrade the access path, never the document identity or evidentiary standard.
- Keep authority, document quality, access health, and retrieval priority as separate judgments.
- A domain's reputation does not grade every item published on it.
- A repost that reproduces the same document is an access carrier, not independent corroboration.
- A summary, interpretation, search snippet, news item, or social post may help discover an original; it must not support a precise recommendation, dose, contraindication, or evidence grade.
Load the relevant references
- For any domestic medical retrieval, read references/domestic-source-registry.md before selecting sources. It defines authoritative scope, discovery-only sources, fallback relationships, and how to extend the registry.
- When a page is blocked, slow, moved, paywalled, incomplete, or unparseable, read references/failover-policy.md before retrying or switching hosts.
- Before using a repost, mirror, alternate PDF, cached copy, or database full text, read references/document-identity.md and verify that it is the same document and version.
Workflow
- Classify the requested fact before searching:
- regulation or legal status;
- approved drug indication, contraindication, dosage, or label;
- pharmacovigilance or adverse-reaction notice;
- reimbursement or payment scope;
- public-health policy, surveillance, or prevention;
- national or industry standard;
- clinical guideline or consensus;
- effectiveness, diagnosis, prognosis, or harm evidence;
- teaching or explanatory material.
- Define the intended document identity from all available fields: normalized title, issuing/developing organization, year/version, document number or DOI, publication venue, and date.
- Use the registry to choose a source authoritative for that fact type. Do not choose solely by generic tier or domain.
- Attempt the canonical route within the retry budget. Classify access failures; do not repeatedly hammer a protected host.
- Follow the failover ladder. Prefer alternate endpoints of the same publisher, official republications, and formal journal versions before verified third-party copies.
- Verify document identity and version before extracting content from any fallback. Reject mismatches and incomplete copies.
- Check for a newer version, correction, update, retraction, or withdrawal before relying on the text.
- Extract only claims supported by the retrieved document. For recommendations, preserve population, intervention, conditions, recommendation strength, evidence certainty, and exceptions when reported.
- Cite the original issuer or formal publication. If a fallback carried the text, disclose the fallback separately instead of presenting it as a second source.
What ships with it
3 files 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.
- 3d ago Changed · +9 lines fe0ab6e8f87a
- 10d ago First seen · 90 lines · 87 tokens per session scan A 1f1d0bba1d3f
medical-source-failover is a skill published in the GitHub repository TencentCloud/Octop (1,513 stars, last pushed today), licensed MIT. It adds 87 tokens to every session and 1,389 once invoked, about $0.0004 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-30.
Other skills, from other repositories
artifact-deploy
One-click deploy a user's pre-built app/artifact into their OWN AWS account and get a global public HTTPS link (Vercel-like), with a default TTL and promote-to-persistent. Use when the user says "deploy this", "ship this demo", "give me a public link", "share this externally", or "deploy to AWS".
explain-for
Explain a topic, a piece of code, an error, or a design decision calibrated to one named audience — a 5-year-old, a 5th grader, a manager, a designer, a graduate student, a parent. Resolves who the explanation is for (from the request, or from what memory already records about that person), establishes the ground…
learn-from-sage
Detection-gap (miss) analysis for Code Review Sage. Learn from shipped fixes, acted-on human comments, and design outcomes to close reviewer blind spots. Inline during review stages a candidate; a human triggers a one-shot AI consolidation into the live ruleset.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.
agent-initialization
Initialize an Agent's settings from a user requirement by writing AGENTS.md, setting identity metadata, and installing only needed Skills.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a…