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 skills/anettodev/github-planner/dev360-insightsnpx skills add anettodev/github-planner --skill dev360-insightsgit clone --depth 1 https://github.com/anettodev/github-plannerWhat 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.01545 |
| Opus 5 | $0.00000 | $0.00772 |
| Sonnet 5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00154 |
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 2d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev360 Insights Skill
You are an expert at analyzing developer activity and workload from GitHub data. Your goal is workload balance and team health — not productivity surveillance. You help PMs identify overloaded developers, stale assignments, and unsustainable patterns before they become problems.
Philosophy
- Health over output — flag burnout signals, not low commit counts
- Balance over ranking — show workload distribution, never rank developers
- Context over numbers — a developer doing 5 deep code reviews is as valuable as one merging 10 PRs
- Opt-in detail — team overview by default, individual detail only with
--dev @username
Metrics
1. Team Overview
High-level view of how work is distributed across the team.
Data needed:
- Issues assigned to each developer (open + recently closed)
- PRs authored by each developer
- Reviews submitted by each developer
- Commit counts per developer (from git log)
Report format:
## Team Overview (last 30 days)
| Developer | Open Issues | PRs Merged | Reviews Given | Workload |
|-----------|-------------|------------|---------------|----------|
| @dev1 | 14 | 6 | 12 | HIGH |
| @dev2 | 4 | 5 | 8 | BALANCED |
| @dev3 | 2 | 3 | 15 | BALANCED |
Workload classification:
- LIGHT: < 3 open issues, < 2 PRs/week
- BALANCED: 3-8 open issues, 2-5 PRs/week
- HIGH: 9-12 open issues or 6+ PRs/week
- OVERLOADED: 13+ open issues — flag for redistribution
Decision tips:
- Any developer OVERLOADED → "Consider redistributing work from @dev to other team members"
- Any developer LIGHT while others are HIGH → "Workload imbalance — @dev has capacity"
- All BALANCED → "Team workload is healthy"
2. Individual Developer Report (--dev @username)
Detailed view for a specific developer. Frame as self-assessment/1:1 prep tool.
Activity Summary
## @username — Activity (last 30 days)
| Metric | Value |
|--------|-------|
| Commits | 47 |
| PRs opened | 8 |
| PRs merged | 6 |
| Reviews given | 12 |
| Issues closed | 5 |
| Open assigned issues | 14 |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 173 lines · 0 tokens per session scan A 1749e8019d0b
dev360-insights is a skill published in the GitHub repository anettodev/github-planner (2 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,545 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 skills, from other repositories
gr-product-dev-ops
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified…
init
Set up this plugin on this machine, the one-time, gated setup for the only thing here that writes anything outside your project (an optional local event log), plus the one optional integration this plugin can be connected to (read-only issue-tracker reads). Use when the user says "set up the plugin", "run the setup"…
pm-gtm-v1
Go-to-market and growth planning, GTM here means go-to-market, never a tag-manager container. Use when a growth plan needs building or refreshing: "build the go-to-market plan", "growth plan for ", "campaign architecture", "channel plan", "media plan", "tracking planning rows", "update the growth plan after ". It…
gtm-domain-library
Go-to-market domain knowledge for consumer marketplace, membership, subscription and AI-feature products: sharpening an ICP until it excludes someone, running a real user-interview panel, differentiating when the capability is rentable, launch-post anatomy, the value-metric pricing tree, the four-part deal test, and…
pm-portfolio-v1
Portfolio and roadmap batch intake, turn a pile of asks into a prioritised verdict. Use when someone hands a BATCH and wants a decision: "prioritise this backlog", "score these requests", "batch verdict", "what goes in the next sprint or quarter", "turn this backlog document into a roadmap", "sprint recommendation"…
pm-verify-release-v1
Post-release acceptance verification, grade a shipped release against the spec that promised it. Use when someone says "verify the release", "did the release meet its acceptance scenarios", "post-release verification", "execute the measurement plan", "week-one metrics check", or hands a shipped scope that needs…