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 BrianV1981/aim --skill switch-github-credsgit clone --depth 1 https://github.com/BrianV1981/aimWrote 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/brianv1981/aim/switch-github-creds)<a href="https://agentmods.dev/skills/brianv1981/aim/switch-github-creds"><img src="https://agentmods.dev/badge/skills/brianv1981/aim/switch-github-creds/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/brianv1981/aim/switch-github-creds"><img src="https://agentmods.dev/badge/skills/brianv1981/aim/switch-github-creds.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.00017 | $0.00333 |
| Opus 5.5 | $0.00007 | $0.00133 |
| Sonnet 5.5 | $0.00003 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
switch-github-creds 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.
What it actually says
<activated_skill>
Skill: switch-github-creds
This skill explains how to switch the active GitHub credentials used by the gh CLI tool when you encounter 403 Forbidden errors or permission issues during git push or other GitHub API operations.
Context
When multiple GitHub accounts are logged in via the GitHub CLI, git commands (if configured to use the gh credential helper) and gh API commands will default to the active account. If you attempt to push to a repository that your active account does not have write access to, you will receive a 403 Forbidden error.
Workflow
-
Check Current Status: Run
gh auth statusto see all logged-in accounts and identify which one is currently active. -
Identify the Correct Account: Determine the username of the account that has permissions to the target repository (e.g.,
BrianV1981). -
Switch the Active Account: Execute the following command to switch the active context to the correct user:
gh auth switch -u <USERNAME>Example:
gh auth switch -u BrianV1981 -
Verify and Execute: After switching, you will see a success message (
✓ Switched active account for github.com to <USERNAME>). You can now safely execute yourgit push origin mainor other GitHub operations.
</activated_skill>
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 · 32 lines · 17 tokens per session scan A 31dc8b8653d3
switch-github-creds is a skill published in the GitHub repository BrianV1981/aim (13 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 333 once invoked, about $0.0001 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
implement
Full implementation mode - end-to-end feature implementation with phased execution, parallel work streams, verification gates, and atomic commits per phase.
commit
Analyze unstaged and staged changes, suggest atomic commit groups with conventional commit messages. NEVER pushes to remote.
release
Author release notes, changelog, and signed release tag.
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…