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 fmind/dot --skill agent-projectgit 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/agent-project)<a href="https://agentmods.dev/skills/fmind/dot/agent-project"><img src="https://agentmods.dev/badge/skills/fmind/dot/agent-project/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/fmind/dot/agent-project"><img src="https://agentmods.dev/badge/skills/fmind/dot/agent-project.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.00024 | $0.00584 |
| Opus 5.5 | $0.00010 | $0.00234 |
| Sonnet 5.5 | $0.00005 | $0.00117 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
agent-project 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up Agents on a Project
Author the shared project instruction and skill layer once, then add only required host bridges. repository-docs owns instruction content; mcp-setup owns MCP configuration.
Workflow
- Inspect first: preserve existing AGENTS.md, host files, skills, and user settings; reuse a stack-specific instruction file when one exists.
- Create the shared layer and bridges: follow host-setup.md to start
AGENTS.mdfrom the project template, add.agents/skills/and the ignored.agents/prompts/inbox for task-prompts, then add Claude links, optional configuration, and native custom-agent locations only for installed hosts. - Verify discovery: read host-discovery.md for listing commands and native plugin catalogs; distinguish presence from demonstrated instruction following.
- Install vendor skills deliberately: follow the shared vendor-skill policy for source review, project scope, versioning, replacement, and the current
skillsversus previewgh skillboundary. Select packages from the dated official skill source audit, which records inspected sources and gaps; recheck the selected source before installation. - Keep current: route repository changes through repository-docs, including project-local skill references.
Task guides
- cross-harness-agents: Decide when a custom agent role pays off, write native definitions per host, and verify discovery.
Gotchas
- Keep one rule body: shared rules live in
AGENTS.md; never add a projectCLAUDE.md, which Claude Code would load instead ofAGENTS.md. - Review repository configuration first: review a repository's hooks, MCP servers, skills, plugins, and custom-agent definitions before enabling them.
What ships with it
6 files 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 Changed 1546f384db38
- 12d ago Changed · -2 lines d280ee1b7380
- 14d ago Changed d7f77893b070
- 15d ago Changed · -6 lines · -3 tokens per session 509ed1adfb80
- 17d ago Changed 3d46047fa78d
- 22d ago Changed · +8 lines 506f315382cc
- 23d ago Changed 67d33f4c2488
- 26d ago Changed d466ed972178
- 29d ago Changed · +6 tokens per session 941a4eb6da56
- 1mo ago First seen · 41 lines · 21 tokens per session scan A 2086f53e9072
agent-project is a skill published in the GitHub repository fmind/dot (12 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 584 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-09-03.
Other skills, from other repositories
github-issues
Manage GitHub issues with gh: confirm repo and state, deduplicate, preserve evidence, and verify authorized creation, edits, labels, comments, or closure.
product-loop
Discovery, specification, launch, and learning for a product in one loop. Build-or-stop calls, MVP wedges, demand tests, customer interviews, PRDs, requirements, user journeys, acceptance, positioning, onboarding, rollout, pricing, pivots.
project-backlog
Turn audit findings into deduplicated, prioritized issue drafts with dependencies and explicit authorization before GitHub mutation.
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…
podio-ticket-updates
Sync in-progress Podio Kanban tickets with progress from their linked GitHub repos — propose description updates and progress comments, apply after approval. Use when the user asks to update Podio tickets, sync ticket progress, or post status updates to the Kanban board.