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 skills/githits-com/githits-cli/githits-codenpx skills add githits-com/githits-cli --skill githits-codegit clone --depth 1 https://github.com/githits-com/githits-cliWhat 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.00059 | $0.01783 |
| Opus 5 | $0.00030 | $0.00892 |
| Sonnet 5 | $0.00012 | $0.00357 |
| Haiku 4.5 | $0.00006 | $0.00178 |
Grade A, and why
githits-code 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 yesterday.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use GitHits for evidence from real open-source code instead of guessing from model memory.
CLI Invocation
- Run commands as
githits .... - If
githitsis not found, retry the same command asnpx -y githits@latest .... - Use
--jsonwhen you need stable fields to parse or chain into another command. - Do not expose credentials. If auth is required interactively, run
githits login; usegithits login --no-browseronly when the user can complete the printed URL flow. In noninteractive eval/CI, do not start OAuth; report thatGITHITS_API_TOKENor prior login is required. - If a command returns
TERMS_ACCEPTANCE_REQUIRED, rungithits settings terms acceptor use the returned authenticated acceptance URL, then retry once.
Decision Flow
- Need a canonical cross-project example or pattern:
githits example "<focused question>"; include source repositories/citations from GitHits' generated references/provenance section whenever present. - Need package metadata, vulnerability/advisory status, dependency graphs, or release notes: stop and use the
githits-packageskill instead. - Exact language name uncertain for
example --lang: rungithits languages <query>first. - Inspecting a known dependency or GitHub repo: start with
githits searchscoped by--in. - Searching an exact standalone documentation site: use
githits search "<topic>" --source docs --in site:<host[/path]>. If the result reports suggested site targets, retry one explicitly; suggestions are advisory targets, not aliases. - Need file/path enumeration: use
githits code files; do not probe directories withcode read. - Know the exact text to match: use
githits code grep(literal by default). Pass--regexfor RE2 syntax; lookaround and backreferences are unsupported. Usegithits searchfor discovery. - Need documentation pages: use
githits search "<topic>" --source docs --in <target>for topic search, orgithits docs list <spec>to browse available pages.
Core Commands
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.
- yesterday First seen · 96 lines · 59 tokens per session scan A c9443e2a35e6
githits-code is a skill published in the GitHub repository githits-com/githits-cli (87 stars, last pushed 3d ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,783 once invoked, about $0.0003 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.
Other skills, from other repositories
kayba-stage-3-metrics
Define metrics from Kayba insights, implement them as Python measurement code, run against traces, and iterate until the metrics are clean and meaningful. Trigger when the user says "run stage 3", "define metrics", "build metrics", "compute baselines", or when invoked by the kayba-pipeline orchestrator. Requires…
kayba-stage-4-rubric
Organize computed metrics into a tiered evaluation rubric with leading, lagging, and quality indicators. Trigger when the user says "run stage 4", "build rubric", "tier metrics", or when invoked by the kayba-pipeline orchestrator. Requires eval/baselinemetrics.json and eval/computebaselines.py to exist.
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-6-hitl
Human-In-The-Loop gate that presents the action plan with full context, collects an informed approval/modification/rejection decision, and records the outcome. Trigger when the user says "run stage 6", "HITL review", "approve action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md…
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.
kayba-stage-7-fixer
Implement the approved fixes from the action plan and log all changes. Trigger when the user says "run stage 7", "implement fixes", "apply action plan", or when invoked by the kayba-pipeline orchestrator. Requires eval/actionplan.md to exist.