Borrowing it
Nothing to install: this file belongs to pillaiharish/opencode-ollama-steroids. 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/pillaiharish/opencode-ollama-steroids/main/.opencode/skills/opencode-ollama-agent-guardrails/SKILL.mdgit clone --depth 1 https://github.com/pillaiharish/opencode-ollama-steroidsWrote 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/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails)<a href="https://agentmods.dev/skills/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails"><img src="https://agentmods.dev/badge/skills/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-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/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-guardrails"><img src="https://agentmods.dev/badge/skills/pillaiharish/opencode-ollama-steroids/opencode-ollama-agent-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.00047 | $0.00398 |
| Opus 5 | $0.00023 | $0.00199 |
| Sonnet 5 | $0.00009 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
opencode-ollama-agent-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 12d 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
OpenCode Ollama Agent Guardrails
Use this skill when configuring, running, reviewing, or publishing an OpenCode + Ollama multi-agent coding workflow.
Required Agent Split
Builder agent:
- plans the current task;
- implements only approved scope;
- runs validation;
- writes implementation notes and test results;
- fixes blocking issues inside scope;
- stops for human review and commit approval.
Reviewer agent:
- reviews builder plans, diffs, tests, generated output, screenshots, and security posture;
- blocks scope creep and weak tests;
- writes only review and signoff files under the current session folder;
- never edits product code.
Hard Rules
- Do not commit, push, rebase, force-push, or start another prompt.
- Do not publish raw prompts, raw OpenCode logs, session exports, or private screenshots.
- Do not use local absolute paths in public-bound files.
- Do not claim success unless the required validation commands passed.
- Do not weaken tests to pass.
- Do not let reviewers edit production code.
- Do not let agents edit resolver-owned prompt model locks ending in
_MODELS.json. - Stop after final signoff so a human can inspect and decide whether to commit.
Session Rules
Use:
agent-sessions/<project-slug>/<prompt-id>/
Product edits belong only under the configured product repo, usually:
product-repo/
Raw logs may stay local in the session folder, but they must remain ignored.
Decision Vocabulary
Reviewer decisions must be exactly one of:
APPROVEDCHANGES_REQUESTEDSIGNED_OFFNOT_SIGNED_OFF
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.
- 12d ago First seen · 63 lines · 47 tokens per session scan A 70acdcd169d7
opencode-ollama-agent-guardrails is a skill published in the GitHub repository pillaiharish/opencode-ollama-steroids (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 398 once invoked, about $0.0002 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
audit-artifact
Interactive workflow for auditing a SpecRoute artifact before it is treated as implementation-ready. Use when checking a PRD, spec triplet, prompt set, agent file, skill, command, hook, rule, or runtime layout. Asks which artifact path to inspect and which contract to apply. Triggers - "audit this artifact", "check…
diff-to-graph
Turns a diff's touched functions and modules into graph nodes, reusing entities the graph already tracks, and links the change itself to each one with a modifies edge.
propose-graph-diff
Turns a proposed addition to a JSON-file graph into a minimal, reviewable diff, flagging any proposed edge that conflicts with a cross-reference already on file, and never writing directly to the shared graph file itself.
all-hands
Convene the relevant SpecRoute implementation agents to plan, collaborate, implement, and review a piece of work end-to-end. Engages only the specialists the work actually touches, runs autonomously through planning into implementation and review, and accepts free-text work or a path to a PRD / spec / issue file.…
doc-currency-check
Audit SpecRoute's documentation for staleness against reality - vendor facts, version anchors, dates written in the wrong tense, counts that no longer match disk, and claims mirrored inconsistently across the four vendor-matrix copies. Use before a release, after any vendor ships a breaking change, or on a scheduled…
frontmatter-lint
Validates YAML frontmatter across SpecRoute artifacts (agents, skills, commands) against the per-artifact contract. Reports missing required fields, malformed YAML, and drift between similar artifacts. Use proactively before commits, when reviewing PRs, or when an agent/skill/command isn't loading correctly.