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/michael-harris/devteam/devteam-issue-newnpx skills add michael-harris/devteam --skill devteam-issue-newgit clone --depth 1 https://github.com/michael-harris/devteamWhat 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.00025 | $0.00850 |
| Opus 5 | $0.00013 | $0.00425 |
| Sonnet 5 | $0.00005 | $0.00170 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
devteam-issue-new 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository: !gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "No GitHub repo detected"
Recent issues: !gh issue list --limit 5 --json number,title,labels -q '.[] | "#\(.number) \(.title) [\(.labels | map(.name) | join(", "))]"' 2>/dev/null || echo "No issues found"
DevTeam Issue New Command
Command: /devteam:issue-new "<description>"
Create a new GitHub issue with proper formatting and labels.
Usage
/devteam:issue-new "Login button not working on mobile"
/devteam:issue-new "Add dark mode support" --label enhancement
/devteam:issue-new "Critical: SQL injection in user search" --label security
Your Process
Step 1: Analyze Description
Parse the issue description from $ARGUMENTS to determine:
Issue type (from keywords):
- "not working", "broken", "error" ->
bug - "add", "implement", "feature" ->
enhancement - "slow", "timeout", "performance" ->
performance - "security", "vulnerability", "injection" ->
security,priority: high - "critical", "urgent" -> add
priority: high
Affected area (if detectable):
- "login", "auth", "user" ->
area: authentication - "API", "endpoint", "request" ->
area: backend - "UI", "button", "page", "mobile" ->
area: frontend - "database", "query", "data" ->
area: database
Step 2: Gather Additional Context
Search codebase for related files and check for similar existing issues:
# Search for related code
grep -r "keyword" --include="*.py" --include="*.ts" -l
# Check for similar issues
gh issue list --search "description keywords"
# Check recent commits in related area
git log --oneline -10 -- related/paths/
Step 3: Format Issue
Create well-structured issue body with:
- Description
- Steps to Reproduce (for bugs)
- Expected vs Actual Behavior (for bugs)
- Proposed Solution (for enhancements)
- Related Code (files found in Step 2)
Step 4: Create Issue
gh issue create \
--title "${title}" \
--body "${body}" \
--label "${labels}"
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 · 107 lines · 0 tokens per session scan A ce508dc3e8ca
devteam-issue-new is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 25 tokens to every session and 850 once invoked, about $0.0001 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-30.
Other skills, from other repositories
scaffold
Set up or align a non-code ops/PM repo with the ops folder structure, CLAUDE.md, and INDEX.md hierarchy.
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-cycle
Run a feature end to end — scout the code, plan it, build it, and keep a session file so a closed terminal doesn't lose the thread.
factory-close
Close out a Linear issue — move to Done, add a closing comment, and clean up the local branch/worktree.
factory-setup-linear
Configure portable Linear workflow settings in .factory-kit/linear.json, migrating legacy .claude/linear.json settings when present.
factory-submit
Move the current branch's Linear issue to "In Review".