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/dotfiles/github-repositorynpx skills add fmind/dotfiles --skill github-repositorygit clone --depth 1 https://github.com/fmind/dotfilesWhat 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.00047 | $0.00935 |
| Opus 5 | $0.00023 | $0.00467 |
| Sonnet 5 | $0.00009 | $0.00187 |
| Haiku 4.5 | $0.00005 | $0.00093 |
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configure GitHub Repository
Inspect a GitHub repository and configure its metadata (description, homepage, topics) and solo-developer settings via gh — clean merge history, secure defaults, and a decluttered UI.
Workflow
Follow these steps to inspect the codebase and apply the configurations:
1. Extract Repository Metadata
Inspect the codebase files to discover or derive the repository metadata:
- Primary Source (Manifests): Check project manifest files:
- Go:
go.mod(undermodulepath for the package/project name). - Python:
pyproject.toml(under[project]fields for name, description, homepage/urls).
- Go:
- Secondary Source (README): Read the
README.mdfirst few paragraphs to extract a concise, high-level description (under ~140 characters). - Homepage URL: Derive from hosting setups (e.g.,
https://<username>.github.io/<repo>for GitHub Pages). - Topics/Tags: Select 3 to 6 descriptive tags representing the main programming language, frameworks, tools, or domain (e.g.,
agent,python,cli).- Constraint: Topics must be lowercase letters, numbers, or hyphens, 50 characters or less, and start with a letter or number (max 20 per repo).
2. Verify GitHub CLI & Inspect Current State
Ensure the GitHub CLI (gh) is authenticated, and fetch the repository's current settings to make changes idempotent:
# Check authentication status
gh auth status
# Get the origin remote URL
git config --get remote.origin.url
# Inspect existing metadata and settings
gh repo view --json description,homepageUrl,repositoryTopics,deleteBranchOnMerge,squashMergeAllowed,mergeCommitAllowed,rebaseMergeAllowed,hasIssuesEnabled,hasProjectsEnabled,hasWikiEnabled,hasDiscussionsEnabled
If the repository does not have an active GitHub remote or gh is not authenticated, report this and halt.
3. Apply Consolidated Configurations
Combine metadata updates and solo developer optimizations into a single consolidated gh repo edit command to maximize speed and efficiency:
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 · 85 lines · 47 tokens per session scan A 3c360d02620b
github-repository is a skill published in the GitHub repository fmind/dotfiles (4 stars, last pushed 2d ago), licensed MIT. It adds 47 tokens to every session and 935 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-08-31.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
aiq-research
Use when asked to run deep research or AI-Q research through a reachable NVIDIA AI-Q Blueprint backend.
obsidian-bases
Obsidian Bases database feature for YAML-based interactive note views. Use when creating .base files, writing filter queries, building formulas, configuring table/card views, or working with Obsidian properties and frontmatter databases.
telegram
Send notifications, interactive questions, or multiple-choice polls to the user via Telegram. Use when the user asks to be notified ("ping me", "notify me on Telegram", "ask me when..."), when a long-running task finishes and the user is likely away, when an irreversible action needs out-of-band confirmation, or when…
chezmoi-expert
Comprehensive chezmoi dotfiles management expertise including templates, cross-platform configuration, file naming conventions, and troubleshooting. Covers source directory management, reproducible environment setup, and chezmoi templating with Go templates. Use when user mentions chezmoi, dotfiles, cross-platform…