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 commands/apideck-libraries/api-skills/list-connectorsgit clone --depth 1 https://github.com/apideck-libraries/api-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/commands/apideck-libraries/api-skills/list-connectors)<a href="https://agentmods.dev/commands/apideck-libraries/api-skills/list-connectors"><img src="https://agentmods.dev/badge/commands/apideck-libraries/api-skills/list-connectors.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00203 |
| Opus 5 | $0.00000 | $0.00102 |
| Sonnet 5 | $0.00000 | $0.00041 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
list-connectors 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 5d 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.
What it actually says
List Apideck Connectors
Show available connectors and their capabilities for a given Apideck unified API:
- Accept the unified API name from arguments (e.g.,
crm,accounting,hris,file-storage,ats) - Use the Vault API to list connections:
vault.connections.list({ api: "<api>" }) - Display each connector with:
- Service ID and name
- Connection state (available, callable, added, authorized, invalid)
- Whether it's currently enabled
- If the user has no connections, suggest opening Vault to set them up
- For each connected service, note which CRUD operations are supported
- Include a link to the full connector coverage at https://developers.apideck.com/apis/connector/reference
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.
- 5d ago First seen · 19 lines · 0 tokens per session scan A 10ad1cdf8115
list-connectors is a command published in the GitHub repository apideck-libraries/api-skills (3 stars, last pushed 6d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 203 tokens. 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 commands, from other repositories
commit
Commit the current changes following the workflow-commit skill — Conventional Commit messages with a worktree-aware commit.sh signing handoff.
security-report
Triage a GitHub code-scanning (CodeQL) finding and write an immutable SHA-pinned report plus index entry, recommending remediation or dismissal.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.