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 zackbart/connecta --skill githubgit clone --depth 1 https://github.com/zackbart/connectaWrote 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/zackbart/connecta/github)<a href="https://agentmods.dev/skills/zackbart/connecta/github"><img src="https://agentmods.dev/badge/skills/zackbart/connecta/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/zackbart/connecta/github"><img src="https://agentmods.dev/badge/skills/zackbart/connecta/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.00001 | $0.01054 |
| Opus 5.5 | $0.00000 | $0.00422 |
| Sonnet 5.5 | $0.00000 | $0.00211 |
| Haiku 4.5 | $0.00000 | $0.00105 |
Grade A, and why
github 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 today.
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.
Setup
Create a GitHub App, generate its RSA private key, and install it on every
configured owner. Org grants require All repositories, including future
repositories. Exact repo grants work with selected-repository installations.
Read-only grants request read permissions; read-write grants request only the
permissions needed by each operation. The App needs repository Metadata,
Contents, Issues, Pull requests, Actions, Checks and Commit statuses for the
reviewed read tools. Grant Contents, Issues, Pull requests and Actions write
only for the operations the deployment needs. Workflow-file edits also need
the App's Workflows write permission and workflows: "write" on the effective
scope. Org grants authorize repository operations, not organization administration.
Pass app: { appId, privateKey } with the key from an environment secret, or
omit privateKey and populate the connector's encrypted privateKey vault field.
Never put private keys or installation tokens in agent instructions. Tokens
stay in bounded runtime memory, refresh a minute before expiry, and are never
persisted. Key rotation partitions the caches by the key's fingerprint.
Configured repository names bind to repository IDs on first use. Bindings last
for the provider instance; name lookups expire after five minutes. A rename
keeps its grant, while a replacement repository at the old name does not.
Reconfigure to authorize a replacement. Transfers leave the original
installation and cannot use its tokens. Org grants bind to installation IDs.
Choose the target first
list_scopes({}) returns configured org/repo grants without network access.
list_scopes({ owner }) resolves that owner's installation and pages reachable
repositories. Carry its next_page. The connection context lists configured
scopes and access. A repo entry overrides and may narrow its parent org entry.
An org grant covers current and future repositories, as long as the installation
keeps All repositories selected.
What ships with it
10 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.
- today Changed f2a4c9ba9406
- 6d ago First seen · 88 lines · 1 tokens per session scan A 3d713e792c38
github is a skill published in the GitHub repository zackbart/connecta (0 stars, last pushed today), licensed MIT. It adds 1 tokens to every session and 1,054 once invoked, about $0.0000 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-10-08.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…