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 commands/developerz-ai/ai-task-master/profilegit clone --depth 1 https://github.com/developerz-ai/ai-task-masterWhat 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.00000 | $0.01253 |
| Opus 5 | $0.00000 | $0.00626 |
| Sonnet 5 | $0.00000 | $0.00251 |
| Haiku 4.5 | $0.00000 | $0.00125 |
Grade A, and why
profile 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aitm profile
Named provider profiles — bundle the provider triple (API key + base URL + per-tier
models) under a name and switch the whole provider in one command, version-manager style
(think nvm use). Profiles live in the global config file ~/.aitm.json under profiles,
with activeProfile naming the one in effect.
See ../providers.md for the provider-switching walkthrough and
../config.md §"Profiles" for how a profile resolves at run time.
Signature
aitm profile list
aitm profile use <name>
aitm profile add <name> [--preset openrouter|zai] [--base-url <url>]
[--api-key <key> | --api-key-stdin]
aitm profile set <name> <key> <value>
aitm profile get <name> <key>
aitm profile remove <name>
aitm profile rename <from> <to>
aitm profile show [<name>]
Profiles are global-only (always written to ~/.aitm.json); there is no --project
selector. <key> for set/get is openrouterApiKey, baseURL, or models.<tier>.
<name> must be non-empty and cannot be __proto__, prototype, or constructor: those name
Object.prototype members, so every subcommand rejects them up front and profile lookups are
own-property only — an inherited key is never mistaken for a profile.
Subcommands
| Command | Effect |
|---|---|
list |
List every profile. * marks the active one; shows base URL + a masked key hint. |
use <name> |
Make <name> the active profile. Errors if the profile doesn't exist (no dangling pointer). |
add <name> |
Create a profile. --preset seeds base URL + models; --base-url / --api-key override. The first profile created auto-activates. Prefer --api-key-stdin (pipe the key) for scripts/CI — a key passed as --api-key is visible in process listings and shell history, so aitm warns when you use it. |
set <name> <key> <value> |
Set one field. Value is JSON-parsed (bare strings stay literal), like config set. |
get <name> <key> |
Print one field's value. |
remove <name> |
Delete the profile. If it was active, activeProfile is cleared. |
rename <from> <to> |
Rename a profile in place, keeping every field. Errors if <from> doesn't exist or <to> already does. If <from> was active, activeProfile is repointed at <to>. |
show [<name>] |
Print a profile as JSON with the key masked. Defaults to the active profile. |
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 · 101 lines · 0 tokens per session scan A f3c214df0435
profile is a command published in the GitHub repository developerz-ai/ai-task-master (5 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,253 tokens. 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 commands, from other repositories
upgrade-webkit
Upgrade Bun's WebKit fork to the latest upstream version of WebKit.
dedupe
Find duplicate GitHub issues.
ashlr-dashboard
Rich token-savings dashboard — per-tool bar charts, 7d/30d sparklines, projected annual savings, and cost in dollars.
scriptwriter-draw
Draw a random chaos card from the 13-card deck — a plot-twist prompt the user can use as a scene seed, a basistext for an RRR cascade, or a riff for a room contribution.
specsync-create-spec
Create a new spec-sync module spec.
nimbus-embedding-routing
Hybrid 384/1536-dim embedding routing (Phase 5 T6 PR 3): PROSEHEAVYTYPES, EMBEDDINGDIMLOCAL/EMBEDDINGDIMOPENAI, the RoutingEmbeddingPipeline wrapper, dual-table search (vecitems384 + vecitems1536 via vectorSearchChunksDual), the V30 migration (1536-dim table + dim-aware delete triggers), the nimbus index reembed CLI +…