Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add pitimon/8-habit-ai-dev/plugin install 8-habit-ai-devWrote 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/pitimon/8-habit-ai-dev/management-talk)<a href="https://agentmods.dev/skills/pitimon/8-habit-ai-dev/management-talk"><img src="https://agentmods.dev/badge/skills/pitimon/8-habit-ai-dev/management-talk/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/pitimon/8-habit-ai-dev/management-talk"><img src="https://agentmods.dev/badge/skills/pitimon/8-habit-ai-dev/management-talk.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.00135 | $0.03130 |
| Opus 5 | $0.00068 | $0.01565 |
| Sonnet 5 | $0.00027 | $0.00626 |
| Haiku 4.5 | $0.00014 | $0.00313 |
Grade A, and why
management-talk 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 9d 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Management Talk (เล่าให้ผู้บริหารฟัง ตามรูปแบบช่องสาร)
Habit: H4 — Think Win-Win + H6 — Synergize | Anti-pattern: Paste a code-heavy JIRA comment into Slack and call it "the update for leadership"
Same source material, shaped for the channel it's going to. The audience is engineering-savvy non-engineers — they read product / framework names and cross-reference JIRA keys and PRs, but they do not read code. The channel decides length, formatting, and how much structure to leave on the page.
When to Use
- After
/post-mortemor any engineering writeup, when the content needs to flow up-the-org or sideways into product/release. - User says "write for management / exec / VP / director / PM / release manager".
- User asks for "executive summary", "leadership update", "status update", "talking points for [meeting]".
- User says "make it less technical / less jargony / less code-heavy".
- User asks for "slack version / standup note / email version" of engineering content.
If the channel is unclear after the trigger, ask one short question — "JIRA, Slack, standup, email, or meeting?" — and stop.
When to Skip
- Audience is true ELI5 / marketing / finance / customer-facing. Engineering-org leadership has technical vocabulary; those audiences don't. Flag and confirm before producing a different rewrite.
- Source content is already non-technical (already a Slack-shape; already an email).
- Engineering content is being written for engineers (use
/post-mortemor/review-aioutput as-is).
Audience — what "engineering-org leadership" means
VPs, directors, PMs, release managers, execs in companies that ship technical products. They want: what's the state, what does it mean for customers, who owns it, what's next. They do not want: how the bug works at the function level.
Tone Rules
Keep. Product names, framework names, team-owned component names, JIRA keys, PR numbers, customer/workload identifiers (PyTorch, vLLM, Llama-2-70B, JIRA-12345, PR #95). These are the bridge between engineering and leadership tracking.
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.
- 9d ago First seen · 231 lines · 135 tokens per session scan A d720aef2937c
management-talk is a skill published in the GitHub repository pitimon/8-habit-ai-dev (3 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 3,130 once invoked, about $0.0007 per session on Opus 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-08-31.
Other skills, from other repositories
review
Business review — weekly health check, monthly close, or ad-hoc audit. Subcommands: weekly, monthly, check. Use for periodic reviews or metrics assessment.
scheduler
Manage scheduled jobs — create, update, list, run remote agents on cron. Use when setting up recurring tasks, checking job status, or managing automation.
do
Alias for /brana:backlog start with freeform text. Routes to the best skill or creates a task. Use /brana:backlog start directly for the same behavior.
backlog
Manage the backlog — plan, track, navigate phases and epics. Use when planning phases, viewing roadmaps, or restructuring work.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
continue
Autonomous work — find and execute ready tasks.