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 apideck-libraries/api-skills --skill githubgit 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/skills/apideck-libraries/api-skills/github)<a href="https://agentmods.dev/skills/apideck-libraries/api-skills/github"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/github/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/apideck-libraries/api-skills/github"><img src="https://agentmods.dev/badge/skills/apideck-libraries/api-skills/github.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.00063 | $0.01996 |
| Opus 5.5 | $0.00025 | $0.00798 |
| Sonnet 5.5 | $0.00013 | $0.00399 |
| Haiku 4.5 | $0.00006 | $0.00200 |
Grade A, and why
github 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 15d 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.
curl 'https://unify.apideck.com/proxy' \ How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub (via Apideck)
Access GitHub through Apideck's Issue Tracking unified API — one of 6 Issue Tracking connectors that share the same method surface. Code you write here ports to Jira, GitLab, Linear and 2 other Issue Tracking connectors by changing a single serviceId string. Apideck handles auth, pagination, rate limiting, and retries so you don't write per-tenant GitHub plumbing.
Beta connector. GitHub is currently in beta on Apideck. Expect partial resource coverage and occasional mapping gaps. Always verify coverage (see below) and fall back to the Proxy API for unsupported operations.
Quick facts
- Apideck serviceId:
github - Unified API: Issue Tracking
- Auth type: oauth2
- Status: beta
- Gotchas: page
- GitHub docs: https://docs.github.com/en/rest
- Homepage: https://github.com/
At a glance
- Implementation difficulty: straightforward — Self-Service GitHub App + Free Account, No Partnership
- Vendor partnership required: no — A GitHub App can be registered under any personal account or organisation you own.
- Apideck-managed credentials: not available — Each customer registers their own GitHub App and supplies its Client ID and Secret.
- Account type required: A GitHub organisation; one organisation per connection.
- Consumer access level: Organisation owner, since only owners can install the GitHub App on the organisation.
- Sandbox: available (signup) — Test with a free GitHub account.
- Rate limits: 5,000 requests per hour per user for a GitHub App acting on a user's behalf; 15,000 per hour when the app is owned by a GitHub Enterprise Cloud organisation.
- Authentication: Authorization Code flow; access follows the GitHub App's permissions, not OAuth scopes.
- Webhooks: Native - issue events (opened, edited, closed, deleted and other issue changes).
Facts synced from Apideck's connector metadata API —
GET /connector/connectors/github(overviewfield) is the live, authoritative version.
What ships with it
1 file 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.
- 15d ago Changed · +17 lines 85659e997115
- 1mo ago First seen · 154 lines · 63 tokens per session scan A 24b99f9c7353
github is a skill published in the GitHub repository apideck-libraries/api-skills (5 stars, last pushed yesterday), licensed Apache-2.0. It adds 63 tokens to every session and 1,996 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
add-azuredevops
Adds Azure DevOps connector to a Power Apps code app. Use when querying work items, creating bugs, managing pipelines, or making ADO API calls.
os-big-picture
ALWAYS invoke this skill when the user asks where the project as a whole stands - "where are we", "what's the big picture", "what have we built", "what is in this project", "map the project", "what does this thing even do", "what is stale", "what can we delete", "update the roadmap" - in any language, and whenever a…
principle-outcome-oriented-execution
Apply during planned rewrites and migrations with explicit phase boundaries. Converge on the target architecture; don't preserve smooth intermediate states with throwaway compatibility code.
manage-flows
Manage flow lifecycle - publish, test, batch operations, inventory reports. Use when the user asks to publish, test, batch manage, or get an inventory of flows.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
catchup
Summarize and review what changed while you were away. Use after a weekend, vacation, or flight to check missed PRs, git commits, Linear tickets, and meetings — one prioritized brief, not a firehose.