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 agentmods add skills/thearchitectit/agent-guardrails-template/docs-accessnpx skills add TheArchitectit/agent-guardrails-template --skill docs-accessgit clone --depth 1 https://github.com/TheArchitectit/agent-guardrails-templateWrote 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/thearchitectit/agent-guardrails-template/docs-access)<a href="https://agentmods.dev/skills/thearchitectit/agent-guardrails-template/docs-access"><img src="https://agentmods.dev/badge/skills/thearchitectit/agent-guardrails-template/docs-access.svg" alt="Measured on agentmods" 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.00023 | $0.00702 |
| Opus 5 | $0.00012 | $0.00351 |
| Sonnet 5 | $0.00005 | $0.00140 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
guardrails-docs-access 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 6d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guardrails Docs Access
Provides runtime access to guardrails skill documentation and configuration guides.
Skill Documentation Index
| Skill | Description | Config Reference |
|---|---|---|
guardrails-core |
Core guardrails lifecycle, tools, and coverage map | .guardrails/config.json |
injection-defense |
Prompt injection detection and blocking | injection.patterns[], injection.confidenceThreshold |
output-security |
Output validation for secrets, PII, and code patterns | outputValidation.rules[] |
content-safety |
Topic-based content filtering (deny/allow lists) | outputValidation.contentFilter.deniedTopics |
tool-permissions |
Per-tool allow/block/ask permission policies | toolPermissions.tools{} |
policy-config |
Dynamic policy management with rollback | policy.name, policy.version |
sandbox-isolation |
Container sandbox configuration and enforcement | sandbox.enabled, sandbox.type |
canary-tokens |
Canary token generation, embedding, and detection | canary.prefix, canary.tokenLength |
guardrails-dashboard |
Dashboard UI for violation monitoring and controls | N/A |
Usage
List All Skills
const skills = guardrail_list_skills(); // Returns array of skill metadata
Read a Specific Skill
const content = guardrail_read_skill({ skill: "injection-defense" }); // Returns SKILL.md content
Read Language Rule Files
const rules = guardrail_read_language_rules({ language: "python" }); // Returns rules JSON
Get Available Languages
const langs = guardrail_list_languages(); // Returns ["python", "typescript", "go", "rust"]
Configuration Templates
Minimal Config
{
"enabled": true,
"enabledRules": ["four-laws", "scope-validator", "halt-when-uncertain"]
}
With Output Validation
{
"enabled": true,
"enabledRules": ["four-laws", "scope-validator", "halt-when-uncertain"],
"outputValidation": {
"enabled": true,
"rules": ["api_key_generic", "aws_access_key"],
"contentFilter": {
"deniedTopics": ["malicious code"]
}
}
}
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.
- 6d ago First seen · 109 lines · 23 tokens per session scan A 37e595e96628
guardrails-docs-access is a skill published in the GitHub repository TheArchitectit/agent-guardrails-template (79 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 23 tokens to every session and 702 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
pydantic-ai
Build production-ready AI agents with PydanticAI — type-safe tool use, structured outputs, dependency injection, and multi-model support.
architecture
Project architecture and file structure conventions for all process types. Use when: (1) Creating new files or modules, (2) Deciding where code should go, (3) Converting single-file components to directories, (4) Reviewing code for structure compliance, (5) Adding new bridges, services, agents, or workers.
testing
Testing workflow and quality standards for writing and running tests. Use when: (1) Writing new tests, (2) Adding a new feature that needs tests, (3) Modifying logic that has existing tests, (4) Before claiming a task is complete.
investigate-issue
Investigate a GitHub issue by fetching details, analyzing the codebase, researching documentation, and presenting an actionable implementation plan with test guidance. Use when asked to investigate, analyze, triage, or plan work for a GitHub issue. Invoked with /investigate-issue or /investigate-issue (prompts for ID).
resolve-pr-comments-stack
Resolve unresolved PR review comments across an entire Graphite (gt) stack of many PRs, bottom-up, in one working directory. Use when asked to "go through this stack and resolve comments", "clean up review comments across the whole stack", or given a list/range of PR numbers that form (or partially form) a gt stack.…
split-commit-into-stack
Split one oversized commit or branch into a stack of independently reviewable Graphite (gt) PRs - deciding what genuinely separates, what is atomic and must stay whole, and proving each lower PR builds and passes without the ones above it. Use when asked to "split this PR", "this commit is too big", "break this into a…