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.
git clone --depth 1 https://github.com/anettodev/github-plannerWrote 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/commands/anettodev/github-planner/dev360-insights)<a href="https://agentmods.dev/commands/anettodev/github-planner/dev360-insights"><img src="https://agentmods.dev/badge/commands/anettodev/github-planner/dev360-insights/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/commands/anettodev/github-planner/dev360-insights"><img src="https://agentmods.dev/badge/commands/anettodev/github-planner/dev360-insights.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.00000 | $0.00485 |
| Opus 5.5 | $0.00000 | $0.00194 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
dev360-insights 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Developer Workload & Health Insights
Analyze developer activity, workload balance, and team health. Focused on sustainability and balance — not productivity surveillance.
Arguments: $ARGUMENTS (optional flags: --repo owner/repo, --dev @username, --period 30d)
Steps
1. Detect Repository
- If
--repoflag provided, use that - Otherwise run
gh repo view --json nameWithOwner -q .nameWithOwner
2. Configure Report Type
Parse flags:
- No
--devflag (default): Team overview — workload distribution and team health signals --dev @username: Individual report — detailed activity, consistency, workload, and health signals for one developer--period 30d(default): Time window for activity metrics
3. Run Analysis
Launch the dev360-analyst agent to:
For team overview:
- Fetch all issues, PRs, commits, and reviews within the period
- Build a profile for each developer (open issues, PRs merged, reviews given)
- Classify workload per developer (Light / Balanced / High / Overloaded)
- Compute team health signals (balance, review culture, sustainability, knowledge sharing, bus factor)
- Generate recommendations
For individual report (--dev @username):
- Fetch all activity for the specified developer
- Compute activity summary (commits, PRs, reviews, issues closed)
- Analyze consistency pattern (weekly breakdown, active days, trend)
- Assess health signals (consistency, weekend work, declining trends)
- Compute contribution patterns (PR size, merge time, review turnaround, self-merge rate)
- List workload (open issues, pending reviews, stale assignments)
- Identify blocked/stale items
- Generate recommendations
4. Present Report
Team overview: Workload table + team health signals + recommendations.
Individual report: Activity summary + work pattern + contribution patterns + workload + blocked items + recommendations.
Use the templates from dev360-insights skill's references/dev360-report.md.
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 · 53 lines · 0 tokens per session scan A 837c05eb74f7
dev360-insights is a command published in the GitHub repository anettodev/github-planner (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 485 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
deep-audit.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects, stack.orm, stack.authmethod Example output.
task-hunter.skeleton
The user's input is resolved according to the following rules.
task-conductor.skeleton
/task-conductor top 5 -> /task-conductor plan top 5 /task-conductor all -> /task-conductor plan all /task-conductor 3,5,8 -> /task-conductor plan 3,5,8.
task-plan.skeleton
ULTRATHINK MODE — This command works with maximum comprehension depth.
bug-review.skeleton
Description: This section will be populated with data from Bootstrap's manifest files. Required manifest fields: project.description, stack.primary, project.structure Example output.
deadcode.skeleton
Description: This section is populated by Bootstrap with manifest data. Required manifest fields: project.description, stack.primary, project.structure, project.subprojects Example output.