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 highflame-ai/zeroid --skill claude-skillgit clone --depth 1 https://github.com/highflame-ai/zeroidWrote 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/highflame-ai/zeroid/claude-skill)<a href="https://agentmods.dev/skills/highflame-ai/zeroid/claude-skill"><img src="https://agentmods.dev/badge/skills/highflame-ai/zeroid/claude-skill/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/highflame-ai/zeroid/claude-skill"><img src="https://agentmods.dev/badge/skills/highflame-ai/zeroid/claude-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 8 findings, 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 101 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.
- high Privilege Escalation · line 113 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.
- high Privilege Escalation · line 131 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.
- high Privilege Escalation · line 155 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.
- high Privilege Escalation · line 245 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.
- high Tool Misuse · line 196 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- high Tool Misuse · line 218 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Data Exfiltration · line 227 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00051 | $0.02897 |
| Opus 5.5 | $0.00020 | $0.01159 |
| Sonnet 5.5 | $0.00010 | $0.00579 |
| Haiku 4.5 | $0.00005 | $0.00290 |
Grade A, and why
zeroid scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
When constructing curl commands, always use this pattern: How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Zeroid — AI Agent Identity Management
You are an interactive assistant for managing agent identities and credentials via the Zeroid REST API. Zeroid assigns agents SPIFFE-based identities (WIMSE URIs), issues OAuth 2.1 tokens, supports delegation chains (RFC 8693 token exchange), and manages credential policies.
Setup
Before making any API calls, verify the environment is configured:
- Check for
ZEROID_BASE_URL(e.g.http://localhost:8899orhttps://auth.highflame.ai). - Check for
ZEROID_API_KEY(azid_sk_...key for authenticating admin API calls). - Check for
ZEROID_ACCOUNT_IDandZEROID_PROJECT_ID(tenant context sent asX-Account-IDandX-Project-IDheaders on admin routes).
If any are missing, ask the user to provide them. Store them as shell variables for the session.
# Verify setup
echo "ZEROID_BASE_URL=${ZEROID_BASE_URL:-not set}"
echo "ZEROID_API_KEY=${ZEROID_API_KEY:-not set}"
echo "ZEROID_ACCOUNT_ID=${ZEROID_ACCOUNT_ID:-not set}"
echo "ZEROID_PROJECT_ID=${ZEROID_PROJECT_ID:-not set}"
Admin routes (/*) may use X-Account-ID and X-Project-ID headers for tenant context if required by the deployment. Public routes (/oauth2/*, /health, /.well-known/*) do not require any tenant headers.
API Reference
Health Check
GET /health -- no auth required.
Returns {"status":"healthy","service":"zeroid","timestamp":"...","uptime_ms":...}.
Use this to verify the server is reachable before performing other operations.
Register an Agent
POST /agents/register -- creates an identity + API key atomically.
Required headers: X-Account-ID, X-Project-ID, Content-Type: application/json.
Request body fields:
name(required) -- human-readable nameexternal_id(required) -- unique identifier within the projectidentity_type(optional) -- one of:agent,application,mcp_server,service(defaults toagent)sub_type(optional) -- one of:orchestrator,autonomous,tool_agent,human_proxy,evaluator,chatbot,assistant,api_service,custom,code_agenttrust_level(optional) -- one of:unverified,verified_third_party,first_party(defaults tounverified)created_by(optional) -- user ID of the creator, becomesownerclaim in tokensframework(optional) -- e.g.langchain,autogen,crewaiversion(optional) -- agent version stringpublisher(optional) -- agent publisher or organizationdescription(optional) -- human-readable descriptioncapabilities(optional) -- JSON array of capabilitieslabels(optional) -- JSON object of key-value labelsmetadata(optional) -- JSON object of opaque product-specific metadatapublic_key_pem(optional) -- PEM-encoded EC P-256 public key for jwt_bearer and token_exchange grants
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.
- 8d ago Changed · +3 lines 04a9dca31b50
- 1mo ago Changed · +2 lines 6d01704850d9
- 1mo ago Changed 4e5ed111ffc7
- 1mo ago First seen · 251 lines · 51 tokens per session scan A 44227ed0083e
zeroid is a skill published in the GitHub repository highflame-ai/zeroid (204 stars, last pushed yesterday), licensed Apache-2.0. It adds 51 tokens to every session and 2,897 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
latchkey
Interact with third-party or self-hosted services (Slack, Google Workspace, Dropbox, GitHub, Linear, Coolify...) using their HTTP APIs on the user's behalf.
jwt
Development guide for the jwt JSON Web Token library for Go (github.com/kataras/jwt). Use this skill when signing or verifying JWTs, choosing a signing algorithm (HMAC, RSA, RSA-PSS, ECDSA, EdDSA), reading or validating standard or custom claims, setting expiry and clock-skew tolerance, rotating keys with a kid-based…
configuring-oauth2-authorization-flow
Configure secure OAuth 2.0 authorization flows including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant. This skill covers flow selection, PKCE implementation, token.
keycloak-migration-doctor
Preflight a Keycloak export, import or migration on a Skycloak-managed cluster against the known blockers, and diagnose a job that already failed by reading the failure reason the API records but the dashboard notice does not show. Use when an export or import fails, a migration stalls, or before moving realm data in…
configuring-oauth2-authorization-flow
Configures secure OAuth 2.0 authorization flows, including Authorization Code with PKCE, Client Credentials, and Device Authorization Grant, covering flow selection, PKCE implementation, token lifecycle management, and scope design per OAuth 2.1. Use when implementing or hardening OAuth 2.0…
api-integration-architect
Design, implement, debug, and optimize API integrations with expert-level patterns for REST, GraphQL, webhooks, and authentication flows.