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 auth-statusgit 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/auth-status)<a href="https://agentmods.dev/skills/fmind/dot/auth-status"><img src="https://agentmods.dev/badge/skills/fmind/dot/auth-status/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/auth-status"><img src="https://agentmods.dev/badge/skills/fmind/dot/auth-status.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.00020 | $0.01312 |
| Opus 5.5 | $0.00008 | $0.00525 |
| Sonnet 5.5 | $0.00004 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
auth-status 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 5d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auth Status
Answer "am I logged in, until when, and what must I run?" with read-only probes, then hand the user the exact interactive command. dot doctor --deep owns the workstation probes; this skill adds the remaining connectors, scope coverage, and recovery. dot-cli authentication owns login policy, scopes, and account overrides; each connector skill owns its provider's account selection.
Workflow
-
Run the workstation probes:
dot doctor --deep --jsonchecks GitHub, the gcloud CLI, ADC, and Workspace with bounded probes and never prints tokens. Read only the auth group;conditiondistinguishesunauthenticatedfrombroken(state unknown) and flagsinsecurewhen gh keeps its token in plaintexthosts.yml.dot doctor --deep --json | jq -c '.checks[] | select(.group == "auth") | {name, status, condition, details}' -
Check scope coverage: compare granted scopes with the configured policy (
dot config show, keysauth.github.scopes,auth.workspace.scopes, andauth.gcp.adc_scopes). GitHub lists them ingh auth status --active --hostname github.com(the token is masked); Workspace ingws auth status | jq '{user, token_valid, has_refresh_token, scopes}'. A missing scope needs a new login even when the probe passes. -
Probe other named connectors: only those the task or user names, each read-only with its exit status checked:
Provider Probe Recovery Colab colab --auth adc sessions(allocates no VM; inspect stderr before trusting an empty list)dot login colabHugging Face hf auth whoamihf auth loginKaggle kaggle competitions list --page-size 1 >/dev/nullkaggle auth loginAWS SSO aws sts get-caller-identity --profile <profile> --no-cli-pageraws sso login --profile <profile>Databricks databricks auth profiles(validates each profile)databricks auth login --host <url> --profile <profile>Atlassian acli auth status; API-token Jira:acli jira auth statusacli auth login
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.
- 5d ago Changed adac4ab04443
- 10d ago Changed · +1 lines 980cac3eb14e
- 11d ago First seen · 60 lines · 20 tokens per session scan A d4b7ab497fc5
auth-status is a skill published in the GitHub repository fmind/dot (11 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,312 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-10-05.
Other skills, from other repositories
google-workspace-cli
Use gws across Workspace APIs with schema-first calls, profile isolation, bounded reads, and verified Drive, Docs, Sheets, Gmail, Calendar, or Chat writes.
handover
Write a self-contained follow-up prompt carrying this session's decisions, constraints, and verified findings into a fresh agent session. Use when handing unfinished work to a new context window.
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…
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…
dotfiles
Chezmoi dotfiles conventions and patterns. Use when modifying dotfiles, adding new managed files, working with chezmoi templates, or syncing agent skills and subagents through agentspec. Do NOT use for installing tools, running doctor, or updating a machine through the dotfiles CLI; use manage-machine.