Borrowing it
Nothing to install: this file belongs to layer1labs/specsmith. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/layer1labs/specsmith/main/.agents/skills/release-governed/SKILL.mdgit clone --depth 1 https://github.com/layer1labs/specsmithWrote 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/layer1labs/specsmith/release-governed)<a href="https://agentmods.dev/skills/layer1labs/specsmith/release-governed"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/release-governed/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/layer1labs/specsmith/release-governed"><img src="https://agentmods.dev/badge/skills/layer1labs/specsmith/release-governed.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.00596 |
| Opus 5.5 | $0.00000 | $0.00238 |
| Sonnet 5.5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
release-governed 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 2mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SKILL.md
Release Governed Profile
Requirements Covered
Governance Requirements
- REQ-012: Least-Privilege Agent Permissions
- REQ-217: Agent Permissions Check
- REQ-220: Policy Guardrails
- REQ-244: Context Window Sizing
- REQ-245: Live Context Fill Indicator
- REQ-246: Auto Context Compression
- REQ-247: Hard Context Ceiling
- REQ-065: GitHub Release Creation
- REQ-066: PyPI Deployment
- REQ-067: CI Management
- REQ-068: Pull Request Management
- REQ-069: GitLab and Bitbucket Support
- REQ-070: Repository Management
- REQ-071: Non-GitHub Platform Support
Core Principle
The release-governed profile is designed for agents operating in release management environments. It ensures compliance with Specsmith governance while managing the complex requirements of software releases across multiple platforms.
Profile Characteristics
Required Skills
- preflight-gate
- governed-agent-loop
- requirement-author
- testcase-author
- traceability-auditor
- context-pack-compiler
- token-budget-auditor
- skill-composer
- git
- release
- execution
Environment-Specific Features
- Release management environment integration
- Context window optimization for release processes
- Compliance with release management policies
- Integration with multiple platform release systems (GitHub, GitLab, Bitbucket, PyPI, etc.)
Implementation Details
Release-Specific Execution
- Leverage release management capabilities for version control and deployment
- Optimize context windows to fit release process constraints
- Apply Specsmith governance rules within release environments
- Maintain traceability between release actions and Specsmith requirements
Context Management
- Optimize context for release management requirements
- Apply release-specific compression techniques
- Ensure context fits within release constraints while maintaining traceability
- Track release management usage and performance metrics
Configuration
Default Behavior
By default, the release-governed profile:
- Integrates with multiple release platforms (GitHub, GitLab, Bitbucket, PyPI)
- Optimizes context for release management processes
- Maintains full Specsmith governance compliance
- Tracks release management metrics
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.
- 2mo ago First seen · 85 lines · 0 tokens per session scan A f26611384fd6
release-governed is a skill published in the GitHub repository layer1labs/specsmith (8 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 596 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-08-31.
Other skills, from other repositories
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
team-release
Orchestrate the release team — release-manager, qa-lead, devops-engineer, producer — to execute a release from candidate to deployment.
changelog-generator
Generate changelogs from git commits. Use when user says "generate changelog", "update changelog", "what changed since last release", or before preparing a new release.
release
Prepare, approve, execute, and independently verify a versioned release through a project-owned exact-command profile.
apply-semantic-versioning
Apply semantic versioning (SemVer 2.0.0) to determine the correct version bump based on change analysis. Covers major/minor/patch classification, pre-release identifiers, build metadata, and breaking change detection. Use when preparing a new release to determine the correct version number, after merging changes…
create-github-release
Create a GitHub release with proper tagging, release notes, and optional build artifacts. Covers semantic versioning, changelog generation, and GitHub CLI usage. Use when marking a stable version of software for distribution, publishing a new library or application version, creating release notes for stakeholders, or…