Borrowing it
Nothing to install: this file belongs to fmind/dot. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fmind/dot/main/.agents/skills/dot-development/SKILL.mdgit 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/dot-development)<a href="https://agentmods.dev/skills/fmind/dot/dot-development"><img src="https://agentmods.dev/badge/skills/fmind/dot/dot-development/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/dot-development"><img src="https://agentmods.dev/badge/skills/fmind/dot/dot-development.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.00022 | $0.00979 |
| Opus 5.5 | $0.00009 | $0.00392 |
| Sonnet 5.5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
dot-development 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Develop Dot
Change the Python CLI while retaining its observable command, archive, and installation contracts. dot-cli owns operating the installed tool; python-stack and cli-contracts own generic implementation and interface design.
Workflow
- Find the owner: inspect
git status --short,git diff, andgit diff --cached, then follow the source/test map below. Read the current implementation before selecting a change boundary. - Define the observable change: preserve command names, aliases, help, JSON output, exit codes, stdout/stderr, and Fish completions unless the task explicitly changes them. Exercise configuration errors through the public CLI; repair commands must remain usable when ordinary config loading fails.
- Implement through existing boundaries: reuse
StateandRunnerfor configuration, streams, and external commands. Use temporary homes and fake runners in tests so a CLI regression cannot authenticate, publish, prune real data, or modify the workstation. - Select proof: run relevant existing tests with
uv run --frozen --project dot pytest -q dot/tests/<test_file>.py; add behavioral cases for changed outcomes and realistic failures. Read session compatibility before changing parser output, replacement rules, or stored formats. - Qualify the candidate: run affected static checks and reuse the focused test results above. Follow project
AGENTS.mdfor the full-gate boundary: shared behavior, dependencies, packaging, or explicit full qualification. Isolate write-formatting checks when unrelated work is present and compare the tested candidate with the intended source before transferring proof or edits. - Verify the right executable: use
uv run --frozen --project dot dot <command>for checkout behavior. When installation is in scope,mise run deployreinstalls it withuv tool install, constrained todot/uv.lock; verifydot --versionand the changed installed command separately.mise run doctoris workstation health, not repository qualification.
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.
- 3d ago Changed cdaaa43f2cde
- 4d ago Changed 962618a6d2e4
- 10d ago Changed 3b66199e00ed
- 16d ago Changed 239ab5975f4a
- 21d ago Changed d792e48acb91
- 23d ago Changed 01ba4b303b46
- 24d ago Changed 90a588fec927
- 26d ago Changed d5814c81b3d0
- 29d ago Changed · +1 lines 00421aeab0bd
- 1mo ago First seen · 41 lines · 22 tokens per session scan A 12b2081b5a3a
dot-development is a skill published in the GitHub repository fmind/dot (12 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 979 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-10.
Other skills, from other repositories
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.
python-script
Write standalone single-file Python scripts using PEP 723 inline metadata and uv. Use when creating a quick CLI script that needs dependencies without a full project.
pytest
Use when writing Python tests with pytest - fixtures, parametrization, markers, conftest layout, pytest-asyncio, pytest-django, coverage with pytest-cov, mocking with pytest-mock, parallel runs with xdist, or CI integration.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
adk-verify-snippets
Checks that every Python code block in a Markdown file actually compiles and runs, by extracting each block to a temporary file, executing it in an isolated subprocess, and writing a pass/fail report with per-snippet coverage. Use when the user asks to verify, test, or validate the code samples in a README, a guide…
adk-setup
Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test run. Runs only when explicitly requested, never on its own. Use when asked to set up, bootstrap, or repair a development…