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 bishopZ/2026-Boilerplate --skill policy-guidegit clone --depth 1 https://github.com/bishopZ/2026-BoilerplateWrote 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/bishopz/2026-boilerplate/policy-guide)<a href="https://agentmods.dev/skills/bishopz/2026-boilerplate/policy-guide"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/policy-guide/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/bishopz/2026-boilerplate/policy-guide"><img src="https://agentmods.dev/badge/skills/bishopz/2026-boilerplate/policy-guide.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.00024 | $0.00384 |
| Opus 5 | $0.00012 | $0.00192 |
| Sonnet 5 | $0.00005 | $0.00077 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
policy-guide 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 10d 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
Policy Guide Updates
Use this skill when changing legal-policy guidance content in the app.
Goal
Maintain one shared page that explains how to author real Terms of Service and Privacy Policy documents for a production deployment.
Files To Update
1) src/client/pages/Policies.tsx
- Update instructional content and section structure.
- Keep the page implementation focused on guidance, not fake legal copy.
- Keep
PageMetatitle/description aligned to content changes.
2) Routing and links
src/client/App.tsx— Ensure/policiesroute renders the guide.src/client/ui/layout/footer.tsx— Keep footer link pointing to/policies.- If legacy URLs are retained (
/privacy,/terms), verify they redirect to/policies.
3) Locale files
- If visible labels change, update all locale JSON files in
src/client/locales/.
4) Sitemap and SEO tests
src/server/controllers/sitemap.ts— Ensure sitemap references/policies.playwright/e2e/seo/page-meta.spec.ts— Keep metadata assertions in sync.
5) Changelog
- Add an
Unreleasedentry for major policy-guide updates.
Validation Checklist
- Run
npm run lint - Run
npm run type-check - Run
npm run test:e2e -- --spec playwright/e2e/seo/page-meta.spec.ts - Verify footer link and legacy routes resolve to
/policies
Done Criteria
- App contains one policy guidance page (
/policies). - Footer and sitemap point to the combined page.
- Metadata + E2E coverage reflect the updated content.
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.
- 10d ago First seen · 53 lines · 24 tokens per session scan A 5ad4e0a3e821
policy-guide is a skill published in the GitHub repository bishopZ/2026-Boilerplate (24 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 384 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
record-upgrade-instructions
Record upgrade instructions alongside a Prisma Next breaking-change PR, so downstream consumers (users of @internal/ and authors of Prisma Next extensions) can apply the matching code translation automatically via the published upgrade skills. Use when you have refactored framework code and the test suite went red in…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
github-review-iteration
Orchestrates a GitHub PR review loop by delegating triage and implementation to dedicated sub-agents, then repeating until actionable review items are cleared. Use when the user says “address PR review”, “triage review comments”, or “iterate until review is clean”.