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 davekilleen/Dex --skill account-plangit clone --depth 1 https://github.com/davekilleen/DexWrote 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/davekilleen/dex/account-plan)<a href="https://agentmods.dev/skills/davekilleen/dex/account-plan"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/account-plan/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/davekilleen/dex/account-plan"><img src="https://agentmods.dev/badge/skills/davekilleen/dex/account-plan.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.00009 | $0.03279 |
| Opus 5.5 | $0.00004 | $0.01312 |
| Sonnet 5.5 | $0.00002 | $0.00656 |
| Haiku 4.5 | $0.00001 | $0.00328 |
Grade A, and why
account-plan 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 1mo 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 — 474 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Create a comprehensive strategic account plan by gathering all context on an account and structuring it into a clear growth and relationship strategy.
Usage
/account-plan [account-name]- Create or update account plan for specific company
Method
Define the account, planning horizon, authorized owner, and as-of time before
searching. Build a source ledger across company, person, meeting, deal, and prior
plan records; deduplicate copied facts while retaining every source ID and source
date. Classify each material item as observed, customer-stated, inferred,
contradictory, stale, or unknown. Only then map stakeholders, current state,
opportunities, risks, and possible actions. Keep recommendations separate from
the account owner's decisions, and never convert a suggested action into a task
or saved plan without the controlled-write sequence below.
Output contract
Return the scope and coverage first, followed by the source ledger, known account
facts, unresolved contradictions and unknowns, stakeholder map, evidence-backed
opportunities and risks, and recommendations awaiting human decision. Any count
or total must name its denominator and excluded unknown values. End with a save
status of not requested, awaiting confirmation, verified from read-back, or
failed, plus the exact path and receipt when a confirmed write occurred. Never
describe an unverified draft as the current account plan.
Evidence, authority, and recovery
Treat the account plan as a decision aid, not as a source of truth. Set an
as-of timestamp when gathering context. Add per-field provenance to every
material fact or claim: the source path or record, the source date (the date of
the event or assertion, or undated), and the as-of time when it was read.
Do not silently use a file modified date as the event date. A compact notation
is: Annual value: £... (source: 04-Projects/..., source date: 2026-08-01, as-of: 2026-08-12T10:30Z).
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.
- 1mo ago First seen · 474 lines · 9 tokens per session scan A 5bcb5cc51315
account-plan is a skill published in the GitHub repository davekilleen/Dex (508 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 3,279 once invoked, about $0.0000 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-02.
Other skills, from other repositories
parallel-feature-development
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing a large feature into independent work streams, when two or more agents need to implement different layers of the same system…
saga-orchestration
Implement saga patterns for distributed transactions and cross-aggregate workflows. Use this skill when implementing distributed transactions across microservices where 2PC is unavailable, designing compensating actions for failed order workflows that span inventory, payment, and shipping services, building…
task-coordination-strategies
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
bazel-build-optimization
Optimize Bazel builds for large-scale monorepos. Use when configuring Bazel, implementing remote execution, or optimizing build performance for enterprise codebases.
nx-workspace-patterns
Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.
context-driven-development
Creates and maintains project context artifacts (product.md, tech-stack.md, workflow.md, tracks.md) in a conductor/ directory. Scaffolds new projects from scratch, extracts context from existing codebases, validates artifact consistency before implementation, and synchronizes documents as the project evolves. Use when…