Agent Safehouse is a macOS sandboxing tool that restricts local AI coding agents to the files and integrations they are allowed to use. It is for developers who want to reduce the damage an agent can cause while preserving normal development workflows. Its catalogue entries help configure or use the sandbox with coding agents.
Borrowing it
Nothing to install: this file belongs to eugene1g/agent-safehouse. 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/eugene1g/agent-safehouse/main/.agents/skills/release/SKILL.mdgit clone --depth 1 https://github.com/eugene1g/agent-safehouseWrote 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/eugene1g/agent-safehouse/release)<a href="https://agentmods.dev/skills/eugene1g/agent-safehouse/release"><img src="https://agentmods.dev/badge/skills/eugene1g/agent-safehouse/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/eugene1g/agent-safehouse/release"><img src="https://agentmods.dev/badge/skills/eugene1g/agent-safehouse/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 Privilege Escalation · line 165 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00057 | $0.03255 |
| Opus 5.5 | $0.00023 | $0.01302 |
| Sonnet 5.5 | $0.00011 | $0.00651 |
| Haiku 4.5 | $0.00006 | $0.00326 |
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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release
Use this skill when the user wants changelog text, release notes, or a CHANGELOG.md update for Agent Safehouse.
This skill is also the canonical local release workflow for Agent Safehouse.
Historical changelog sections are append-only by default. Do not rewrite, normalize, or reformat older release entries to match a newer structure unless the user explicitly asks for a changelog migration or cleanup pass.
This skill is responsible for proposing the next release version from the last published release.
The repo-root VERSION file is the canonical version source for Agent Safehouse.
Write the selected version into VERSION and into the new CHANGELOG.md heading unless the user explicitly gives a different target version.
Default to a stable release. Only choose a prerelease version such as -rc.N or -beta.N when the user explicitly asks for a prerelease.
If the user explicitly gives the target version, honor it even if the default SemVer analysis would have chosen a different bump. In that case, note briefly in the dry run that the version came from an explicit user override.
Workflow
-
Resolve the baseline release. If the user gives a starting version, use it. Otherwise:
- Prefer the latest published stable GitHub release tag from
gh release list --exclude-drafts --exclude-pre-releases. - Ignore draft releases.
- Ignore prereleases such as
-rc,-beta, and other hyphenated SemVer suffixes unless the user explicitly asks to prepare a prerelease. - If GitHub release metadata is unavailable, fall back to the latest stable SemVer git tag.
- Prefer the latest published stable GitHub release tag from
-
Decide the next SemVer version from the release range. Start from the resolved baseline release and choose:
majorfor breaking changes, incompatible CLI behavior, removed capabilities, changed defaults that are likely to break existing setups, or sandbox/policy tightening that requires user action to restore a previously supported workflow.minorfor backward-compatible new features, new integrations, new profiles, new user-visible capabilities, or meaningful expansions of supported workflows.patchfor bug fixes, non-breaking sandbox/profile corrections, docs, tests, internal cleanup, and other maintenance-only changes.- If the range mixes features and fixes but nothing breaking, choose
minor. - If the range is ambiguous and there is no clear breaking change or new feature, choose
patch. - If you choose
major, explicitly state why in the drafted release notes. - If the user explicitly asks for a prerelease, first choose the target stable version using the rules above, then append the requested prerelease suffix such as
-rc.1or-beta.1. - If the user explicitly asks for another prerelease in the same series, increment that series from the latest matching non-draft prerelease tag or release, for example
1.4.0-rc.1to1.4.0-rc.2.
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 · 217 lines · 57 tokens per session scan A fa90783b3249
release is a skill published in the GitHub repository eugene1g/agent-safehouse (2,121 stars, last pushed 6d ago), licensed Apache-2.0. It adds 57 tokens to every session and 3,255 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
github-repo-management
Clone, create, fork, configure, and manage GitHub repositories. Manage remotes, secrets, releases, and workflows. Works with gh CLI or falls back to git + GitHub REST API via curl.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
changelog
Turn a range of commits or merged PRs into a changelog entry grouped by change type. Use when the user asks for release notes, a changelog, or "what changed" between two points.
otto-drive-pr
PR mergeability, CI, and live preview.
github-auth
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.
goal-release
Cut a release end to end: use the draft-release skill to open the release PR and draft GitHub release, wait for CI to turn green, run the merge-pr skill to merge the release PR, then update the Homebrew formula from the published release assets. Use when the user wants to draft and merge a release in one go, or…