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 FortiumPartners/ensemble --skill staleness-gategit clone --depth 1 https://github.com/FortiumPartners/ensembleWrote 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/fortiumpartners/ensemble/staleness-gate)<a href="https://agentmods.dev/skills/fortiumpartners/ensemble/staleness-gate"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/staleness-gate/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/fortiumpartners/ensemble/staleness-gate"><img src="https://agentmods.dev/badge/skills/fortiumpartners/ensemble/staleness-gate.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.00000 | $0.01602 |
| Opus 5 | $0.00000 | $0.00801 |
| Sonnet 5 | $0.00000 | $0.00320 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
staleness-gate 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRD Staleness Gate
Detect whether a TRD is stale before implementation begins. If stale, invoke
/ensemble:refine-trd to refresh it, then proceed. If refinement fails, halt.
Inputs
| Variable | Type | Description |
|---|---|---|
TRD_PATH |
string | Absolute or repo-relative path to the TRD .md file |
IS_RESUME |
boolean | true when implementation is resuming an existing scaffold; false on first invocation |
FLAVOR |
string | Calling command name (for diagnostic messages): implement-trd-beads, implement-trd, or beads-build |
Resume Detection by Flavor
| Flavor | IS_RESUME = true when |
|---|---|
implement-trd-beads |
ROOT_EPIC_ID found in br list --json for this TRD slug (Preflight step 6 — Resume Detection) |
implement-trd |
git branch --list feature/<TRD_SLUG>-sprint-1 returns a branch name (checked before branch creation) |
beads-build --trd |
ROOT_EPIC_ID found in Epic Discovery step (Preflight step 4) |
Algorithm
Step 1 — Resume Check
IF IS_RESUME == true:
print "Staleness check: skipped (resume detected)"
RETURN
Staleness detection does not apply to resuming an existing scaffold. The TRD was already validated on first invocation; checking it again mid-session would block legitimate resume operations.
Step 2 — Get TRD mtime
Determine the last-modified time of the TRD file as a Unix epoch integer.
# macOS
TRD_MTIME=$(stat -f %m "<TRD_PATH>")
# Linux
TRD_MTIME=$(stat -c %Y "<TRD_PATH>")
# Fallback (cross-platform, if stat not available or fails)
TRD_MTIME=$(python3 -c "import os; print(int(os.path.getmtime('<TRD_PATH>')))")
Try macOS form first; if it fails (non-zero exit or empty output), try Linux form; if that fails, try the Python fallback.
IF all three methods fail:
print "WARNING: Cannot determine TRD file age — skipping staleness check."
RETURN
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 · 206 lines · 0 tokens per session scan A f4030bd577ca
staleness-gate is a skill published in the GitHub repository FortiumPartners/ensemble (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,602 tokens. 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-09-03.
Other skills, from other repositories
context-recovery
Recovers project handoff context from local Codex, Claude Code, Gemini, CodeBuddy, and codexmate-derived sessions. Use when the user asks what happened in prior project/PR/branch/file/error work, needs a handoff brief, wants old decisions or validations recovered, or asks to summarize cross-session project activity…
dev
This skill should be used when the user asks to start, restart, keep alive, or inspect the local pikiclaw development service, including npm run dev, local debug bot startup, dashboard verification, and dev log checks.
overleaf
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
bmad-quick-dev-new-preview
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
bmad-check-implementation-readiness
Validate PRD, UX, Architecture and Epics specs are complete. Use when the user says "check implementation readiness".
bmad-create-story
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]".