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 using-agentstackgit 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/using-agentstack)<a href="https://agentmods.dev/skills/tarekkharsa/agentstack/using-agentstack"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/using-agentstack/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/using-agentstack"><img src="https://agentmods.dev/badge/skills/tarekkharsa/agentstack/using-agentstack.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.00054 | $0.00926 |
| Opus 5.5 | $0.00022 | $0.00370 |
| Sonnet 5.5 | $0.00011 | $0.00185 |
| Haiku 4.5 | $0.00005 | $0.00093 |
Grade A, and why
using-agentstack 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use AgentStack
Start with the state
Run agentstack status first. Use agentstack doctor only when status points to
a problem or deeper verification is needed.
Read these facts separately:
locked: portable content is pinned; this does not mean a connection is live.trusted: a human approved the current manifest and lock on this machine.default toolset: what a trusted new agent connection opens automatically.live toolset: a process-scoped connection that exists right now.delivery: which capabilities are served live and which are written to files.
Follow the delivery decision
When status says skills or MCP servers are served live:
- Do not run
use,apply, orrender-locallyto make them appear. - Do not create
.mcp.json,.claude/skills/,.agents/skills/, or similar capability folders. - Use the trusted default toolset. If several toolsets exist without a default, ask the user which one should be selected.
- The connection already receives loadable skill names and one-line
descriptions. Refresh or filter them with
agentstack_list_loadable(query). - Load only a needed full body with
agentstack_load(name, reason). The user does not need to say the skill name when its description clearly matches. - Discover proxied runtime tools and their schemas with
tools_searchonly when the task needs one.
File-only CLIs and capability kinds are rendered automatically. An explicit
render_locally override is a compatibility choice, not the normal live path.
Change the source of truth only
- Change
.agentstack/agentstack.toml, legacyagentstack.toml, or the personal library. Never hand-edit generated provider configuration. - Keep secret values out of manifests and libraries. Declare
${REF}and tell the user to runagentstack secret set REFon each machine. - After changing selected skills or servers, preview with
agentstack lock. Useagentstack lock --writeonly with authorization. - Never run
agentstack trustfor the user. Show what changed and leave the consent action to the human. - Preview any write. Do not add
--writeunless the user explicitly authorized that AgentStack change. - Respect policy and guard refusals. Explain them; never retry around them.
What ships with it
3 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.
- 1mo ago First seen · 88 lines · 54 tokens per session scan A a27857438298
using-agentstack is a skill published in the GitHub repository Tarekkharsa/agentstack (3 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 926 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
terraform-setup
Install (deploy) MCP Gateway & Registry on AWS using the Terraform aws-ecs stack (ECS Fargate, Aurora, DocumentDB, Keycloak). Asks whether you are running from an EC2 instance or a local laptop, confirms the required AWS IAM permissions are in place, clones the repository, bootstraps the toolchain (uv, AWS CLI…
macos-setup
Complete macOS setup and teardown for MCP Gateway & Registry (AI-registry). Clones the repository, installs all services, configures Keycloak auth, registers the Cloudflare docs server, and verifies the full stack. Also supports complete teardown. Can be run directly from its GitHub URL without the repository already…
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.
pr-review
Review a GitHub pull request using multiple expert personas. Takes a PR URL as input, analyzes the changes, and generates comprehensive review feedback from different perspectives (Merge Specialist, Frontend, Backend, Security, DevOps, AI/Agent, SRE, Chief Architect).
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.
writing
Write prose people will actually read. Use for any prose you produce - docs, READMEs, release notes, blog posts, PR descriptions, issue text, commit bodies, design docs, emails, chat answers. Applies Orwell's six rules and strips the LLM tells - passive voice, dead metaphors, and -ly padding.