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/bobbyjohnstx/tinycode/releasenpx skills add bobbyjohnstx/tinycode --skill releasegit clone --depth 1 https://github.com/bobbyjohnstx/tinycodeWrote 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/bobbyjohnstx/tinycode/release)<a href="https://agentmods.dev/skills/bobbyjohnstx/tinycode/release"><img src="https://agentmods.dev/badge/skills/bobbyjohnstx/tinycode/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.00024 | $0.02191 |
| Opus 5 | $0.00012 | $0.01095 |
| Sonnet 5 | $0.00005 | $0.00438 |
| Haiku 4.5 | $0.00002 | $0.00219 |
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 yesterday.
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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
End-to-end release workflow for the tinycode ecosystem. Covers version bump, changelog, documentation, GitHub release, container image, and operator update.
When to use
- Cutting a new tinycode release (e.g.,
/release v1.18.0) - The user says "release", "cut a release", "ship it", "new version"
Prerequisites
Before starting, verify:
- Working tree is clean (
git status— no uncommitted changes) - All tests pass (
bun testfrompackages/tinycode/) - Type check passes (
bun typecheckfrompackages/tinycode/) - You're on the
mainbranch
If any prerequisite fails, stop and report. Do not proceed with a dirty tree or failing tests.
Phase 1: Determine Version
If $1 was provided, use it (strip leading v for package.json, keep v prefix for tags).
If no version was provided, check the current version in packages/tinycode/package.json and the git log since the last release tag. Determine the appropriate bump:
- patch (x.y.Z) — only bug fixes
- minor (x.Y.0) — new features present
- major (X.0.0) — breaking changes
Confirm the version with the user before proceeding.
Phase 2: Changelog
- Run
git log --onelinefrom the last release tag to HEAD - Categorize commits into Added, Changed, Fixed, Security sections
- Update
CHANGELOG.md:- Move items from
[Unreleased]into a new[version] — YYYY-MM-DDsection - Add all new commits not already in Unreleased
- Keep the
[Unreleased]header with empty sections for future work
- Move items from
Phase 3: Version Bump
Bump version in ALL package.json files. They must stay in sync:
grep -rn '"version":' packages/*/package.json
Update every one to the new version. There are typically 8 packages:
packages/tinycode/package.jsonpackages/app/package.jsonpackages/desktop/package.jsonpackages/plugin/package.jsonpackages/llm/package.jsonpackages/ui/package.jsonpackages/http-recorder/package.jsonpackages/effect-drizzle-sqlite/package.json
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.
- yesterday First seen · 215 lines · 24 tokens per session scan A c489f7987800
release is a skill published in the GitHub repository bobbyjohnstx/tinycode (12 stars, last pushed 2d ago), licensed MIT. It adds 24 tokens to every session and 2,191 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-09-04.
Other skills, from other repositories
system-prompts
Write system prompts, tool docs, and agent definitions. Project tag conventions + RFC 2119 keywords + dense compression. Use when authoring or editing any prompt the model reads.
tool-prompt-optimization
Optimize the description prompts an AI agent reads to learn its built-in tools (the .md files under prompts/tools/). Two halves: (1) measure how much of a prompt is already inferable from the tool's JSON parameter schema + name, to prune redundancy with evidence; (2) house authoring rules for what belongs in a tool…
semantic-compression
Re-encode verbose prose into a dense telegraphic register — punctuation as connectives, label frames, verbless assertions — without losing normativity or precision. Use when compressing system prompts, tool/function descriptions, skill bodies, or agent instructions; reducing token count or context bloat; making…
greet
A greeting skill for testing.
release
Create a release from dev branch. Generates changelog entries from commits, bumps version, and creates a PR to main. TRIGGERS - Use this skill when user says: "/release" - create a patch release (default) "/release minor" - create a minor release "/release major" - create a major release "make a release", "cut a…
release-rome-image
Release a new Rome runtime image by pushing a vX.Y.Z tag — pick the version, verify main is releasable, push the tag, and confirm the image published to Docker Hub. Covers the v runtime-image tag only, not the desktop app (desktop-v) and not npm packages (ui-v, app-runtime-v).