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/sgroy10/speclock/speclock-guardrailsnpx skills add sgroy10/speclock --skill speclock-guardrailsgit clone --depth 1 https://github.com/sgroy10/speclockWrote 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/sgroy10/speclock/speclock-guardrails)<a href="https://agentmods.dev/skills/sgroy10/speclock/speclock-guardrails"><img src="https://agentmods.dev/badge/skills/sgroy10/speclock/speclock-guardrails.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.00063 | $0.00336 |
| Opus 5 | $0.00032 | $0.00168 |
| Sonnet 5 | $0.00013 | $0.00067 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
speclock-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 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.
What it actually says
SpecLock Guardrails
Use SpecLock as an action-verification layer. It complements memory, skills, reviews, and tests; it does not prove factual correctness or eliminate hallucinations.
Workflow
- Read the project briefing and active SpecLock constraints before changing files.
- Check the intended action, affected files, and commands for conflicts.
- Stop on a blocking violation. Proceed only when an authorized user explicitly identifies the constraint to amend or override; do not infer override permission from a conflicting implementation request.
- Check the resulting patch or diff before presenting or committing it.
- Record material constraint decisions when the project uses SpecLock decision history.
- Preserve Git or CI enforcement as the universal fallback when the client cannot intercept actions natively.
Boundaries
- Treat MCP-only integrations as assisted verification, not guaranteed interception.
- Never claim that SpecLock makes generated code correct or hallucination-free.
- Do not weaken or delete locks without explicit authorization.
- Do not send private project data to a remote service without consent.
Decision output
Report ALLOW, WARN, or BLOCK, followed by the relevant constraint, planned action, affected files or commands, reason, and safest next step. Direct contradiction with an active constraint is BLOCK; ask for clarification when a semantic match is uncertain.
What ships with it
1 file 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.
- 6d ago First seen · 29 lines · 63 tokens per session scan A 561f82a70eab
speclock-guardrails is a skill published in the GitHub repository sgroy10/speclock (25 stars, last pushed 18d ago), licensed MIT. It adds 63 tokens to every session and 336 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-30.
Other skills, from other repositories
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.
memorix-troubleshooting
Use when Memorix MCP, setup, project binding, HTTP control plane, hooks, skills, or agent integration is missing, stale, or failing.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.