Atomic Agents is a lightweight, modular framework for assembling AI agents and applications from single-purpose components such as agents, tools, and context providers. It is for developers building maintainable agentic AI pipelines with reusable, composable parts and structured outputs. The catalogue entries provide agent skills, instructions, settings, and related development workflows for the framework.
Borrowing it
Nothing to install: this file belongs to Eigenwise/atomic-agents. 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/Eigenwise/atomic-agents/main/.claude/skills/release/SKILL.mdgit clone --depth 1 https://github.com/Eigenwise/atomic-agentsWrote 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/eigenwise/atomic-agents/release)<a href="https://agentmods.dev/skills/eigenwise/atomic-agents/release"><img src="https://agentmods.dev/badge/skills/eigenwise/atomic-agents/release/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/eigenwise/atomic-agents/release"><img src="https://agentmods.dev/badge/skills/eigenwise/atomic-agents/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 59 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00043 | $0.00672 |
| Opus 5.5 | $0.00017 | $0.00269 |
| Sonnet 5.5 | $0.00009 | $0.00134 |
| Haiku 4.5 | $0.00004 | $0.00067 |
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 1mo 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Process for atomic-agents
Overview
This skill guides the release process for atomic-agents, including version bumping, PyPI publishing, and GitHub release creation.
Prerequisites
- Must be on
mainbranch with clean working directory .envfile must containPYPI_TOKENenvironment variable- Must have push access to the repository
Release Types
| Type | When to Use | Example |
|---|---|---|
major |
Breaking changes | 2.5.0 → 3.0.0 |
minor |
New features (backwards compatible) | 2.5.0 → 2.6.0 |
patch |
Bug fixes only | 2.5.0 → 2.5.1 |
Step-by-Step Process
1. Prepare the Branch
git checkout main
git pull
git status # Ensure clean working directory
2. Run Build and Deploy Script
Important: The script bumps versions, so if it fails partway through, reset to main before retrying.
powershell -ExecutionPolicy Bypass -File build_and_deploy.ps1 <major|minor|patch>
This script will:
- Read current version from
pyproject.toml - Increment version based on release type
- Update
pyproject.tomlwith new version - Run
uv syncto update dependencies - Run
uv buildto create distribution packages - Run
uv publishto upload to PyPI
3. If Script Fails - Reset and Retry
git checkout main
git reset --hard origin/main
# Fix the issue, then run script again
4. Commit and Push Version Bump
git add pyproject.toml uv.lock
git commit -m "Release vX.Y.Z"
git push
5. Create GitHub Release
gh release create vX.Y.Z --title "vX.Y.Z" --notes "RELEASE_NOTES_HERE"
Release Notes Template
## What's New
### Feature Name
Brief description of the feature.
#### Features
- Feature 1
- Feature 2
#### Improvements
- Improvement 1
#### Bug Fixes
- Fix 1
### Full Changelog
https://github.com/eigenwise/atomic-agents/compare/vOLD...vNEW
Checklist
- On main branch with clean working directory
-
.envfile hasPYPI_TOKEN - Determined correct release type (major/minor/patch)
- Build and deploy script completed successfully
- Version bump committed and pushed
- GitHub release created with release notes
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.
- 1mo ago First seen · 107 lines · 43 tokens per session scan A 20e7c455a718
release is a skill published in the GitHub repository Eigenwise/atomic-agents (6,287 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 672 once invoked, about $0.0002 per session on Opus 5.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
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. Ends with the agent running npm publish itself using the maintainer's npm…
childhood
Babysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.
build-and-release
Fully automate building and releasing a coding task.
release
Fully automate a release with version-bump and childhood.
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.