Borrowing it
Nothing to install: this file belongs to omar-A-hassan/medsci-agent. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/omar-A-hassan/medsci-agent/main/.opencode/skills/operational-guardrails/SKILL.mdgit clone --depth 1 https://github.com/omar-A-hassan/medsci-agentWrote 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/omar-a-hassan/medsci-agent/operational-guardrails)<a href="https://agentmods.dev/skills/omar-a-hassan/medsci-agent/operational-guardrails"><img src="https://agentmods.dev/badge/skills/omar-a-hassan/medsci-agent/operational-guardrails/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/omar-a-hassan/medsci-agent/operational-guardrails"><img src="https://agentmods.dev/badge/skills/omar-a-hassan/medsci-agent/operational-guardrails.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.00027 | $0.00761 |
| Opus 5 | $0.00014 | $0.00380 |
| Sonnet 5 | $0.00005 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
Grade A, and why
operational-guardrails 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.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Operational Guardrails
These rules apply to every MedSci agent session. They override any conflicting behavior.
1. Planning Phase (Before Any Tool Call)
Before your first tool call, produce a brief plan:
- Classify the task type (lookup, analysis, synthesis, code execution).
- Identify which toolchains are needed and in what order.
- List data dependencies between steps.
- State stop conditions — what constitutes "done" and what would trigger an abort.
- Estimate evidence depth — is one tool call enough, or is multi-step synthesis required?
Only then begin executing. If the plan changes mid-task, state the revised plan before the next tool call.
2. Sequential Execution (No Exceptions)
Execute all MCP tool calls one at a time. Wait for each result before calling the next tool.
Why: MedGemma and TxGemma run locally inside MCP tools. Parallel calls queue on the same local model, causing MCP timeouts (error -32001).
Prohibited language in plans: Never write "I can run these in parallel", "these steps are independent", "simultaneously", or "at the same time" for tool calls. Every step executes sequentially — perceived independence is irrelevant. Write your plan as a numbered sequence and execute step 1 immediately after the plan.
3. Retry and Stop Policy
- Per-tool retry limit: 1 retry on transient failure (timeout, rate limit). If it fails twice, skip it.
- Session retry limit: No more than 3 total retries across all tools in one session.
- Continue with partial data when a non-critical tool fails. Note the gap explicitly.
- Halt and ask the user when a critical-path tool fails twice (e.g., the only data source for the query).
- Never retry on permanent errors:
CLI_UNAVAILABLE,ARTIFACT_PATH_FORBIDDEN,MODEL_NOT_FOUND.
4. Model Interpretation Fallback
When a tool returns model_used: false (MedGemma/TxGemma unavailable):
- Return the raw data — it still has value.
- Provide your own interpretation clearly labeled as "LLM interpretation (not domain model)."
- Do not silently omit the raw data in favor of your interpretation.
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 · 27 tokens per session scan A 7752562934db
operational-guardrails is a skill published in the GitHub repository omar-A-hassan/medsci-agent (18 stars, last pushed 4d ago), licensed MIT. It adds 27 tokens to every session and 761 once invoked, about $0.0001 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
llm-integration
LLM integration patterns for function calling, streaming responses, local inference with Ollama, and fine-tuning customization. Use when implementing tool use, SSE streaming, local model deployment, LoRA/QLoRA fine-tuning, or multi-provider LLM APIs.
paseo-plugin
Build and manage trusted local Paseo plugins. Use when the user asks to create, edit, install, reload, enable, disable, remove, or troubleshoot a Paseo plugin; add lifecycle hooks; transform agent configuration, environment, MCP servers, or workspace creation; automate permissions or turn follow-ups; add a native…
paseo
Paseo reference for managing projects, workspaces, workspace scripts, agents, schedules, and heartbeats.
paseo-help
Answer questions about the Paseo product and app, including setup, configuration, connectivity, providers, workspaces, updates, logs, and troubleshooting. Use when a user inside Paseo asks how Paseo works, how to configure it, or why something is broken; use the paseo skill instead to operate agents and workspaces…
paseo-advisor
Spin up a single agent as an advisor — second opinion on the current task. Use when the user says "advisor", "second opinion", "what does X think", or wants an outside take without delegating the work itself.
paseo-handoff
Hand off the current task to another agent with full context. Use when the user says "handoff", "hand off", "hand this to", or wants to pass work to another agent.