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 agentmods add skills/openscribbler/syllago/releasenpx skills add OpenScribbler/syllago --skill releasegit clone --depth 1 https://github.com/OpenScribbler/syllagoWrote 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/openscribbler/syllago/release)<a href="https://agentmods.dev/skills/openscribbler/syllago/release"><img src="https://agentmods.dev/badge/skills/openscribbler/syllago/release.svg" alt="Measured on agentmods" 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 | $0.00032 | $0.00740 |
| Opus 5 | $0.00016 | $0.00370 |
| Sonnet 5 | $0.00006 | $0.00148 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
release 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 4d 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release
Interactive two-phase release workflow for syllago. Analyzes changes, recommends a version bump, writes release notes, and ships — with human approval at every decision point.
Arguments
No arguments required. The skill determines the version interactively.
Semver Guidelines
Use these criteria when recommending a release type. Present these in the AskUserQuestion options so the user sees the reasoning.
Major (X.0.0)
- Breaking changes to CLI commands (renamed/removed subcommands, changed flags, changed output format)
- Breaking changes to
.syllago.yamlschema that require user migration - Breaking changes to registry protocol or content format
- Dropping support for a provider
- Any change that would break existing scripts or workflows using syllago
Minor (0.X.0)
- New features (commands, subcommands, TUI screens, content types)
- New provider support
- Non-breaking additions to config format or
.syllago.yaml - Significant improvements to existing features (new options, expanded behavior)
- New built-in content (skills, agents, etc.)
Patch (0.0.X)
- Bug fixes
- Performance improvements with no behavior change
- Documentation corrections that ship with the binary (help text, etc.)
- Dependency updates with no user-facing impact
- Minor UX polish (typo fixes, better error messages)
Pre-1.0 Note
While syllago is pre-1.0, minor versions may include small breaking changes if needed. After 1.0, semver is strict — breaking changes require a major bump.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| create-release | /release |
workflows/create-release.md |
Flow Overview
/release
1. Analyze changes since last release (git log + diffstat)
2. AskUserQuestion: release type (major/minor/patch) with reasoning
3. Write release notes from template
4. AskUserQuestion: approve release notes
5. Bump VERSION, commit, create .release-pending.yml (status: prepared)
6. AskUserQuestion: ship it?
7. Tag, push, create GitHub Release, delete .release-pending.yml
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 84 lines · 32 tokens per session scan A 18eec2b0ed35
release is a skill published in the GitHub repository OpenScribbler/syllago (15 stars, last pushed yesterday), licensed Apache-2.0. It adds 32 tokens to every session and 740 once invoked, about $0.0002 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
go-safe-move-refactor
Safely move Go source files between packages with zero compilation downtime. Handles package declarations, import updates, symbol exports, type renames, test migration, and forwarding stubs. Validates compilation after every atomic step.
go-source-documentation
Add idiomatic, godoc-compliant documentation to Go source and test files. Use when user asks to document Go files, add doc comments, improve Go documentation, or mentions /document-go. Covers file headers, package comments, types, functions, interfaces, constants, variables, tests (with detailed explanations)…
increase-test-coverage
Increase Go test coverage to 90%+ using a Research → Plan → Implement pipeline. Analyzes coverage gaps, generates table-driven tests with httptest mocks, and validates results with go test -coverprofile. Designed for Go MCP server projects using the official go-sdk and gitlab.com/gitlab-org/api/client-go/v2.
modularize-go-package
Modularize a monolithic Go package into domain-specific sub-packages. Extracts shared utilities, moves domain files, updates imports, renames types, creates registration functions, and validates compilation+tests at every step. Designed for large-scale refactoring of 50-100+ file packages.
create-mcp-tool
Create a new MCP tool end-to-end: sub-package, input/output structs, handler, ActionSpec metadata, markdown formatter, tests, catalog projection, and documentation. Use when adding a new GitLab API endpoint as an MCP tool.
generate-project-documentation
Generate comprehensive project documentation including architecture overview, package/component docs, MCP tools/resources/prompts reference, developer onboarding guide, and configuration/deployment guide. Uses Diátaxis framework and Mermaid diagrams.