rosetta github-api-auth.instructions.md

Repository instructions requiring authenticated GitHub API requests through the project's shared helper functions.

In plain words
What is it for?
Use them when writing GitHub integrations, fetching repository files, or running extraction scripts in local development and CI.
Why use it?
They prevent rate-limit failures caused by unauthenticated GitHub requests and keep repository file downloads on the supported API path.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/tikoci/rosetta/github-api-auth
Clone the repo
git clone --depth 1 https://github.com/tikoci/rosetta

Made for: GitHub Copilot.

Per session 333 This file is loaded in full into every session.
When invoked 333 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00333 $0.00333
Opus 5 $0.00167 $0.00167
Sonnet 5 $0.00067 $0.00067
Haiku 4.5 $0.00033 $0.00033

Measured 2d ago against content hash c32ea41e061d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rosetta github-api-auth.instructions.md 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 2d 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.

.github/instructions/github-api-auth.instructions.md · 13 lines

What it actually says

GitHub API calls must be authenticated

Any code that talks to api.github.com (or fetches repo file contents) must go through fetchGitHub() + githubApiHeaders() in src/github.ts, not a bare fetch().

  • Never call raw.githubusercontent.com — it's unauthenticated and rate-limited separately from the API. Use the Contents API (/repos/{owner}/{repo}/contents/{path}?ref={sha}) with Accept: application/vnd.github.v3.raw instead.
  • CI steps that run extraction scripts hitting GitHub must set GITHUB_TOKEN: ${{ github.token }} in their env: block (see release.yml).
  • Locally, githubApiHeaders() falls back to GH_TOKEN if GITHUB_TOKEN isn't set. Run local extraction with GH_TOKEN=$(gh auth token) bun run src/extract-skills.ts to avoid tripping the unauthenticated 60 req/hr limit.
  • This isn't hypothetical: the unauthenticated limit was hit in production once the corpus (RouterOS versions + skill files) grew past ~50 GitHub API calls per release run. See PR #16.
Changes

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.

  1. 2d ago First seen · 13 lines · 333 tokens per session scan A c32ea41e061d

Subscribe to this mod's changes

rosetta github-api-auth.instructions.md is an instructions file published in the GitHub repository tikoci/rosetta (43 stars, last pushed 15d ago), licensed MIT. It adds 333 tokens to every session, about $0.0017 per session on Opus 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.

Related

Other instructions, from other repositories