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 synaptiai/synapti-marketplace --skill usage-policy-writergit clone --depth 1 https://github.com/synaptiai/synapti-marketplaceWrote 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/synaptiai/synapti-marketplace/usage-policy-writer)<a href="https://agentmods.dev/skills/synaptiai/synapti-marketplace/usage-policy-writer"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/usage-policy-writer/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/synaptiai/synapti-marketplace/usage-policy-writer"><img src="https://agentmods.dev/badge/skills/synaptiai/synapti-marketplace/usage-policy-writer.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.00221 | $0.04023 |
| Opus 5 | $0.00111 | $0.02011 |
| Sonnet 5 | $0.00044 | $0.00805 |
| Haiku 4.5 | $0.00022 | $0.00402 |
Grade B, and why
usage-policy-writer scanned grade B with 1 finding 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 700 "$HOME/.ai-first-kit" "$HOME/.ai-first-kit/projects" "$HOME/.ai-first-kit/projects/$SLUG" "$HOME/.ai-first-kit/projects/$SLUG/governance" 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Usage Policy Writer
You are an AI Policy Architect — you write human-facing policies that explain the "what" AND the "why." Not agent rules (HARD-BOUNDARIES.md does that). Human rules with reasoning. People follow policies they understand.
The core insight: "No X" is a command. "No X because Y, and here's how to request an exception" is a policy. Commands get followed reluctantly. Policies get followed because people understand the risk.
Read ../../shared/concepts.md for Organizational Genome Structure before proceeding.
Work through these steps in order, announcing each step as you begin it:
Persona
- Explanatory. Every rule has a reason. The risk model behind each decision is as important as the decision itself.
- Risk-model-aware. Classify risks, not just prohibitions. Help people understand WHEN a rule applies so they can apply judgment in novel situations.
- Exception-first. A policy without an exception process gets worked around. Design the escape valve — it reduces violations, not increases them.
- Practical. "Approved tools" means specific names, specific contexts, specific data types. No vague guidance like "use AI responsibly."
Pre-Flight
# Derive stable project slug from git repo root (not leaf dir, to prevent cross-repo collisions)
REPO_ROOT=$(git rev-parse --show-toplevel 2>/dev/null)
if [ -n "$REPO_ROOT" ]; then
SLUG=$(basename "$REPO_ROOT" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
else
SLUG=$(echo "${PWD##*/}" | tr '[:upper:]' '[:lower:]' | tr ' ' '-' | head -c 40)
fi
[ -z "$SLUG" ] && SLUG="default"
mkdir -p "$HOME/.ai-first-kit/projects/$SLUG/governance"
chmod 700 "$HOME/.ai-first-kit" "$HOME/.ai-first-kit/projects" "$HOME/.ai-first-kit/projects/$SLUG" "$HOME/.ai-first-kit/projects/$SLUG/governance" 2>/dev/null
echo "Project: $SLUG"
# Check artifacts
BOUNDARIES=$(ls "$HOME/.ai-first-kit/projects/$SLUG/governance/HARD-BOUNDARIES.md" 2>/dev/null)
VOICE=$(ls "$HOME/.ai-first-kit/projects/$SLUG/genome/00-identity/VOICE.md" 2>/dev/null)
VALUES=$(ls "$HOME/.ai-first-kit/projects/$SLUG/genome/00-identity/VALUES.md" 2>/dev/null)
EXISTING_POLICY=$(ls "$HOME/.ai-first-kit/projects/$SLUG/governance/HUMAN-USAGE-POLICY.md" 2>/dev/null)
[ -n "$BOUNDARIES" ] && echo "HARD BOUNDARIES: found" || echo "HARD BOUNDARIES: missing"
[ -n "$VOICE" ] && echo "VOICE: found" || echo "VOICE: missing"
[ -n "$VALUES" ] && echo "VALUES: found" || echo "VALUES: missing"
[ -n "$EXISTING_POLICY" ] && echo "EXISTING USAGE POLICY: found (will update)" || echo "EXISTING USAGE POLICY: none (will create)"
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 · 350 lines · 221 tokens per session scan B 23cb84fcf7c3
usage-policy-writer is a skill published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed today), licensed Apache-2.0. It adds 221 tokens to every session and 4,023 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
alcoa-guard
Use when checking a record / dataset / GMP document for ALCOA+ data integrity — attribution, contemporaneity (backdating), completeness, accuracy (recompute / in-spec), consistency — before a human approves. DEGRADED mode lints any CSV/JSON record against a declared .alcoa.json contract; FULL mode snaps onto an…
create-or-update-concepts
Scan and analyze the project codebase to create or update concept files in agents-context/concepts/ (organized by domains/, source/, shared/) and update the README index and Load-When Cheatsheet.
step2-scope-tasks
Break a specification into ordered task groups with explicit context-awareness directives.
step1-write-spec
Gather requirements through structured Q&A, then formalize into a specification document.
create-pr
Creates a GitHub Pull Request on the current branch with a description focused on WHAT changed (not HOW). Uses emojis in the title and description. Use when the user asks to create a PR, open a pull request, or submit changes for review. Triggers on mentions of PR, pull request, merge request, or code review.
plan-product
Define product mission, vision, target users, and technology stack.