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 skills add Tarekkharsa/agentstack --skill sync-librarygit clone --depth 1 https://github.com/Tarekkharsa/agentstackWrote 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/tarekkharsa/agentstack/sync-library)<a href="https://agentmods.dev/skills/tarekkharsa/agentstack/sync-library"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/sync-library/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/tarekkharsa/agentstack/sync-library"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/sync-library.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.00046 | $0.00743 |
| Opus 5.5 | $0.00018 | $0.00297 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00005 | $0.00074 |
Grade A, and why
sync-library 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sync the central library
Use when you want your agentstack central library — the skills and MCP servers you reference by name — to be the same on every machine (laptop, desktop, a fresh box).
The idea
The library lives at ~/.agentstack/lib/. Version it as a git repo and
push/pull it across machines. git is the right tool here: versioned,
offline-friendly, no daemon, and it diffs cleanly.
Never fetch a skill from another machine by hand (scp/rsync/ssh). A raw copy skips the content scan (prompt-injection gate), records no provenance, and has no checksum — an unauditable fork the lockfile can't reproduce. If a skill you need lives on another device, sync the library (below); the skill then resolves by name everywhere.
The built-in way (preferred)
agentstack ships a wrapper that does the whole flow — and refuses to push if a
server definition holds a literal secret in any field (headers, env, url,
args), can't be parsed (the gate fails closed rather than skipping it), or if
one is still buried in an outgoing commit. --allow-secrets overrides,
deliberately:
# first machine — set it up and push:
agentstack more lib sync --init --remote <your-remote>
agentstack more lib sync # commit local changes, pull, push
# a fresh machine — clone the library into place:
agentstack more lib sync --init --remote <your-remote>
agentstack more lib sync --status # working-tree changes + ahead/behind
What travels vs. what doesn't
- Travels:
library.toml(the index),skills/(path-source bodies),servers/(definitions with${REF}placeholders only). - Stays local: the content store / cache lives outside the library
(
~/.agentstack/store), so it never travels; resolved secret values are never in the library at all.
Git-source skills carry git:<url>@<rev>#<subpath> provenance, so they
re-resolve identically on any machine — only path-source content needs to move.
Doing it by hand (equivalent)
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 · 85 lines · 46 tokens per session scan A 0337a67a22f4
sync-library is a skill published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 743 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-31.
Other skills, from other repositories
release-notes
Create release notes for a new version tag. Gathers all commits, PRs, issues fixed, and breaking changes since a previous release. Creates the release notes markdown file, tags the repo, and pushes. Asks the user to confirm the base version to diff against.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.