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 preset-io/agent-skills --skill preset-admingit clone --depth 1 https://github.com/preset-io/agent-skillsWrote 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/preset-io/agent-skills/preset-admin)<a href="https://agentmods.dev/skills/preset-io/agent-skills/preset-admin"><img src="https://agentmods.dev/badge/skills/preset-io/agent-skills/preset-admin/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/preset-io/agent-skills/preset-admin"><img src="https://agentmods.dev/badge/skills/preset-io/agent-skills/preset-admin.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.00045 | $0.00537 |
| Opus 5.5 | $0.00018 | $0.00215 |
| Sonnet 5.5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
preset-admin 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
preset-admin
Use for Preset Management API administration beyond read-only workspace discovery.
Always
- Auth and conventions come from
preset-api(JWT exchange, base URLs, Rison); resolve the workspace hostname through the Management API when it is not already known. - Default to read-only preflight and ID/role lookup.
- Resolve team, workspace, user, invite, and role identifiers from API responses before mutations.
- Get explicit confirmation before role changes, invites, member removals, workspace lifecycle actions, audit downloads, or any write.
- Use
preset-roles-permissionsfor permission-sensitive role/access changes.
Decision Rules
- Classify membership role and invite changes as approval-gated mutations.
- Use metadata reads for membership, role, invite, and audit inspection.
- Require target and effect summary before any access change.
- Avoid applying invite or member role changes until approval is explicit.
Workflow Order
- Identify team, workspace, user, invite, member, and role identifiers.
- Inspect membership, role, invite, and audit metadata.
- Prepare approval summary with target and expected effect.
- Stop before invite, member role, removal, or workspace change.
Retrieve
- Team membership routing: references/team-memberships.md
- Team member lookup, seat checks, response fields: references/team-member-lookup.md
- Team role changes and removals: references/team-member-access-changes.md
- Workspace create/update/delete/un-hibernate: references/workspace-management.md
- Invites, cancellation, resend, bulk invite: references/invites.md
- Audit log lookup and downloads: references/audit-logs.md
- Role identifiers: references/role-identifiers.md
- Unsupported or adjacent Manager endpoints: references/deferrals.md
- Approval policy before writes/downloads: load
preset-apiand thenreferences/safety-policy.md.
What ships with it
9 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.
- examples/team_memberships.py 1.1 KB runs code
- references/audit-logs.md 5.1 KB
- references/deferrals.md 2.2 KB
- references/invites.md 4.9 KB
- references/role-identifiers.md 3.5 KB
- references/team-member-access-changes.md 1.3 KB
- references/team-member-lookup.md 1.6 KB
- references/team-memberships.md 1.1 KB
- references/workspace-management.md 7.8 KB
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 · 47 lines · 45 tokens per session scan A 35283401f007
preset-admin is a skill published in the GitHub repository preset-io/agent-skills (13 stars, last pushed 18d ago), licensed Apache-2.0. It adds 45 tokens to every session and 537 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
docs-governance
Route broad documentation-governance requests to existing ECC skills and run an opt-in, read-only audit of mapped documentation roles, links, ADR indexes, and evidence references. Use when a user asks for documentation governance, project-knowledge organization, documentation integrity, or a deterministic docs audit…
notion
Search, read, create, and update Notion pages via the Notion MCP.
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
meeting-action-items
Turn meeting notes into cited decisions, owners, tickets.
create-stories
Breaks one epic into implementable stories with acceptance criteria. Use when the user wants stories for an epic or the next batch of work to build. Not for turning the whole design into epics.
day-one-patch
Day-one launch patch — focused fix for known issues found after gold master. Mini-sprint with QA gate and rollback.