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/agentscope-ai/agentteams/github-operationsnpx skills add agentscope-ai/AgentTeams --skill github-operationsgit clone --depth 1 https://github.com/agentscope-ai/AgentTeamsWhat 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.00050 | $0.02231 |
| Opus 5 | $0.00025 | $0.01115 |
| Sonnet 5 | $0.00010 | $0.00446 |
| Haiku 4.5 | $0.00005 | $0.00223 |
Grade A, and why
github-operations 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 — 405 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub PR & Issue Management
Overview
This skill allows you to manage Pull Requests and Issues via the centralized MCP Server. For git operations (clone, pull, push, commit, branch), use the git-delegation skill instead.
Environment Variables
No environment variables needed — mcporter reads its config from the default path ./config/mcporter.json automatically.
| Task | Use This Skill | Use git-delegation |
|---|---|---|
| Create/update/close PR | ✅ | |
| Review/merge PR | ✅ | |
| Comment on PR/Issue | ✅ | |
| Create/update/close Issue | ✅ | |
| Clone repository | ✅ | |
| Pull/fetch changes | ✅ | |
| Read/write files | ✅ | |
| Create branches | ✅ | |
| Commit/push code | ✅ |
How to Call GitHub Tools
Use mcporter CLI to call MCP Server tools:
# Method 1: key=value format (recommended for simple args)
mcporter \
call mcp-github.<TOOL_NAME> key1=value1 key2=value2
# Method 2: JSON format with --args flag (for complex objects)
mcporter \
call mcp-github.<TOOL_NAME> --args '{"key1":"value1","key2":"value2"}'
IMPORTANT:
- Always place
--configBEFORE thecallsubcommand - For JSON arguments, use the
--argsflag (not bare JSON string) - Use
mcp-github.<tool_name>selector format
Output
mcporter returns JSON output. Parse with jq for clean results.
Pull Request Operations
create_pull_request
Create a new Pull Request:
mcporter \
call mcp-github.create_pull_request --args '{
"owner": "higress-group",
"repo": "agentteams",
"title": "Add new feature",
"body": "## Summary\n- Change 1\n- Change 2\n\n## Test plan\n- [ ] Test A\n- [ ] Test B",
"head": "feature-branch",
"base": "main"
}'
list_pull_requests
List PRs in a repository:
mcporter \
call mcp-github.list_pull_requests owner=higress-group repo=agentteams state=open
get_pull_request
Get details of a specific PR:
mcporter \
call mcp-github.get_pull_request owner=higress-group repo=agentteams pull_number=1
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 · 405 lines · 50 tokens per session scan A ce81842a6bc9
github-operations is a skill published in the GitHub repository agentscope-ai/AgentTeams (5,537 stars, last pushed 11d ago), licensed Apache-2.0. It adds 50 tokens to every session and 2,231 once invoked, about $0.0003 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
plan-ceo-review
CEO/founder-mode plan review. Rethink the problem, find the 10-star product, challenge premises, expand scope when it creates a better product. Four modes: SCOPE EXPANSION (dream big), SELECTIVE EXPANSION (hold scope + cherry-pick expansions), HOLD SCOPE (maximum rigor), SCOPE REDUCTION (strip to essentials). Use when…
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, and create a PR. Use for an explicit /ship invocation or when the user requests the full ship, release, or deploy workflow. For an ordinary commit, push, or pull-request publishing request, use the built-in…
design-review
Designer's eye QA: finds visual inconsistency, spacing issues, hierarchy problems, AI slop patterns, and slow interactions — then fixes them. Iteratively fixes issues in source code, committing each fix atomically and re-verifying with before/after screenshots. For plan-mode design review (before implementation), use…
plan-eng-review
Eng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when…
pre-landing-review
Pre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when explicitly asked for the specialized pre-landing workflow. Product /review requests are handled by BitFun's unified Review mechanism instead.…
autoplan
Auto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when…