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/fmind/dot/github-repositorynpx skills add fmind/dot --skill github-repositorygit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/github-repository)<a href="https://agentmods.dev/skills/fmind/dot/github-repository"><img src="https://agentmods.dev/badge/skills/fmind/dot/github-repository.svg" alt="Measured on agentmods" 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 | $0.00037 | $0.00766 |
| Opus 5 | $0.00018 | $0.00383 |
| Sonnet 5 | $0.00007 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
github-repository 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Repository
Derive a repository's description, homepage, and topics from its codebase and apply them with gh repo edit together with solo-developer settings: squash-only merges, secure defaults, a decluttered sidebar.
Workflow
-
Extract metadata from the codebase:
- Manifests: Go
go.mod(modulepath), Pythonpyproject.toml([project]name, description, urls), TypeScriptpackage.json(name,description,homepage). README.md: the first paragraphs give a one-line description under ~140 characters.- Homepage: derive from hosting, e.g.
https://<owner>.github.io/<repo>for GitHub Pages. - Topics: 3 to 6 lowercase tags for language, frameworks, tools, or domain (
agent,python,cli); letters, numbers, and hyphens only, 50 characters max, 20 per repository.
- Manifests: Go
-
Inspect the current state so the edit stays idempotent; stop when there is no GitHub remote or
ghis not authenticated:gh auth status git config --get remote.origin.url gh repo view --json description,homepageUrl,repositoryTopics,deleteBranchOnMerge,squashMergeAllowed,mergeCommitAllowed,rebaseMergeAllowed,hasIssuesEnabled,hasProjectsEnabled,hasWikiEnabled,hasDiscussionsEnabled -
Apply one consolidated edit; append
--enable-issues=falseonly when the project tracks issues elsewhere:gh repo edit \ --description "<description>" \ --homepage "<homepage-url>" \ --add-topic "tag1,tag2,tag3" \ --delete-branch-on-merge \ --enable-squash-merge \ --squash-merge-commit-message pr-title-description \ --enable-merge-commit=false \ --enable-rebase-merge=false \ --allow-update-branch \ --enable-secret-scanning \ --enable-secret-scanning-push-protection \ --enable-wiki=false \ --enable-projects=false \ --enable-discussions=false -
Verify with the same
gh repo view --json ...call and report the fields that changed.
Gotchas
- Truncation: keep the description single-line and under ~140 characters or the GitHub UI truncates it.
- Advanced Security: secret-scanning push protection is free for public and personal private repositories; organization-owned private repositories may need GitHub Advanced Security.
- Visibility: never pass
--visibilityor--accept-visibility-change-consequencesunless the user explicitly asks.
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 · 63 lines · 37 tokens per session scan A e85e89b1be8d
github-repository is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 766 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
mise
Configure pinned mise tools and canonical install, format, check, test, build, and watch tasks shared by hooks and CI.