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/tarekkharsa/agentstack/using-agentstacknpx skills add Tarekkharsa/agentstack --skill using-agentstackgit clone --depth 1 https://github.com/Tarekkharsa/agentstackWhat 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.00054 | $0.00926 |
| Opus 5 | $0.00027 | $0.00463 |
| Sonnet 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 3d 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.
- 3d 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 20d ago), licensed Apache-2.0. It adds 54 tokens to every session and 926 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
release-notes
Edit an existing GitHub release's body into the project's bilingual (English + Chinese) template format with a References section built from merged PRs. Use when 修改 release、整理发布说明、release notes、编辑 release 内容、发版后整理、edit release body.
new-feature-design
Design and document new features with GitHub issue, low-level design (LLD), expert review, and testing plan. Creates structured documentation in .scratchpad/ with issue spec, technical design with diagrams and pseudo-code, multi-persona expert review, and a testing plan covering functional (curl and…
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.
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).