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 alicicek/tale-mode --skill seed-gatesgit clone --depth 1 https://github.com/alicicek/tale-modeWrote 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/alicicek/tale-mode/seed-gates)<a href="https://agentmods.dev/skills/alicicek/tale-mode/seed-gates"><img src="https://agentmods.dev/badge/skills/alicicek/tale-mode/seed-gates/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/alicicek/tale-mode/seed-gates"><img src="https://agentmods.dev/badge/skills/alicicek/tale-mode/seed-gates.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.00085 | $0.00873 |
| Opus 5 | $0.00043 | $0.00436 |
| Sonnet 5 | $0.00017 | $0.00175 |
| Haiku 4.5 | $0.00009 | $0.00087 |
Grade A, and why
seed-gates 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 9d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Seed the committed gates (suggest-only)
Help the user pick the gates for a committed .claude/tale-mode.json — the config tale-mode's
Stop hook enforces during a kickoff phase (once the user trusts its content-hash; see the trust
skill). Your output is a suggestion the user reviews — never silently write the config, and never
touch the trust store.
1. Inventory candidates mechanically — don't guess from memory
Read the repo's own definition of "green":
- every
package.json→ thescriptsblock (root first; workspaces if a monorepo) - CI workflows →
.github/workflows/*.yml(or the host's equivalent) — the commands CI actually runs are the strongest signal of what "passing" means here - other manifests as present:
Makefile,pyproject.toml/tox.ini,Cargo.toml,go.mod(→go test ./...), a repo-localtests/runner script
2. Filter hard — a gate runs at EVERY turn-end during a phase
Keep only commands that are hermetic and terminating:
- ✅ local + deterministic: typecheck (
tsc --noEmit), lint, format-check, unit tests, a build that's reasonably fast, a repo-local test script - ❌ anything that doesn't terminate:
dev,start,serve,--watch - ❌ anything non-hermetic: network calls, fresh dependency installs, deploy/publish/release, E2E needing a live server or credentials, destructive/generative steps (db migrations, codegen that rewrites files — a gate must be read-only/idempotent, it runs repeatedly)
- ❌ anything slow enough to hurt: the default per-gate timeout is 120s (
TALE_CHECK_TIMEOUT); a 10-minute suite belongs in CI, not a turn-end gate - Each gate runs as ONE shell script — a multi-line JSON string is allowed (it executes as a single script, not split per line), but prefer one command per gate for readable failure output.
3. Verify each candidate by RUNNING it, then present
Run every surviving candidate once from the repo root and record its exit code. A suggested gate that can't run (missing dep, wrong path) — or that always fails — is worse than none: it would trap the loop, and the user would "fix" it by weakening the config. Drop or flag anything that isn't green on the current tree, and say why.
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.
- 9d ago First seen · 66 lines · 85 tokens per session scan A 9fe67cf60966
seed-gates is a skill published in the GitHub repository alicicek/tale-mode (36 stars, last pushed 2mo ago), licensed MIT. It adds 85 tokens to every session and 873 once invoked, about $0.0004 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
guards-setup
A setup guide for installing automatic code-quality checks, such as linting, type checking, dependency-cycle checks, and optional CI checks.
craft-infra
The Craftsman standard for production infrastructure — deployment, env/config, CI/CD, IaC, health/readiness, scaling, platform/edge rate limiting, build/release, rollback. Use WHENEVER work touches infra: deploy, CI gates, env vars, IaC, load failures, platform rate limiting, pooling runtime constraints, or production…
sw-guard
Detects project stack and existing guardrails, then interactively configures deterministic quality checks across session, commit, push, and CI/CD layers.
configure-env-variables
Configures environment variables for Power Pages site settings to support ALM across environments. Creates environment variable definitions in Dataverse, guides the user through linking site settings to those variables via the Power Pages Management app, adds the variables to the solution, and generates a…
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
new-skill
Scaffold a new brooks-lint analysis skill so it passes npm run validate and npm run evals on the first try — generates skills/{name}/SKILL.md (with the mandatory "Do NOT trigger for:" clause and a Process section citing guide step ranges) plus skills/{name}/{name}-guide.md (sequentially numbered steps), then appends…