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 avizmarlon/agent-skills --skill business-guardrailsgit clone --depth 1 https://github.com/avizmarlon/agent-skillsWrote 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/avizmarlon/agent-skills/business-guardrails)<a href="https://agentmods.dev/skills/avizmarlon/agent-skills/business-guardrails"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/business-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/avizmarlon/agent-skills/business-guardrails"><img src="https://agentmods.dev/badge/skills/avizmarlon/agent-skills/business-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.00052 | $0.01203 |
| Opus 5 | $0.00026 | $0.00602 |
| Sonnet 5 | $0.00010 | $0.00241 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
business-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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Business Guardrails — Validation Before Development
This skill enforces product strategy discipline for AI agents working on business and product projects. Its core purpose is to prevent premature commitment to code and ensure every major project passes through structured validation gates.
Core Rules
1. Never Skip Validation to Jump Straight to Code
Every new product or feature faces a mandatory validation phase before any implementation work begins. Validation includes:
- Market research — Are paying customers willing to use this? Is there demand?
- Competitive analysis — Who else is solving this problem? What are their gaps?
- ICP & USP definition — Who is the ideal customer? What is the differentiated value?
- Scope definition — What is actually in the MVP vs. future iterations?
Validation is NOT optional and NOT an afterthought. It comes first.
2. No Scope Creep Without Explicit Approval
MVP scope is fixed. Any suggestion to add features, extend functionality, or change requirements must:
- Be proposed to the decision-maker explicitly (not silently added to the design)
- Include trade-offs: what ships on-time, what slips, what cost increases?
- Require explicit written approval before implementation
Anti-pattern: "We could also include X..." followed immediately by implementation. This pattern breaks predictability and burns time. Propose, wait for approval, then build.
3. Contextualize Every New Project Within Existing Portfolio
When starting a new project, ask:
- How does this fit with other active projects?
- Does it complement, compete with, or cannibalize existing work?
- Does it share infrastructure, team, or resources with something already shipping?
- What's the opportunity cost?
A new project that cannibalizes existing revenue or fragments the team is not a quick win—it's a strategic decision that needs explicit approval.
4. Competitive Analysis Must Be Substantive
"I didn't find any competitors" without evidence is rejected. Substantive analysis means:
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 · 111 lines · 52 tokens per session scan A 397f93aa32a4
business-guardrails is a skill published in the GitHub repository avizmarlon/agent-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,203 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.