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 skills add Emasoft/ai-maestro-architect-agent --skill amaa-github-integration-opsgit clone --depth 1 https://github.com/Emasoft/ai-maestro-architect-agentWrote 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/emasoft/ai-maestro-architect-agent/amaa-github-integration-ops)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-github-integration-ops"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-github-integration-ops.svg" alt="Measured on agentmods" 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.00036 | $0.00535 |
| Opus 5 | $0.00018 | $0.00267 |
| Sonnet 5 | $0.00007 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
amaa-github-integration-ops 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 6d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Integration Operations
Overview
Operational references for GitHub integration: CLI authentication, edge case handling, status-to-label mapping, troubleshooting, and design lifecycle workflow.
Prerequisites
- Core GitHub integration skill (
amaa-github-integration) understood
Instructions
- Verify gh CLI auth using the verification procedure reference
- Handle edge cases (duplicate issues, missing UUIDs, CLI unavailable)
- Use status mapping to manage design-to-label synchronization
- Follow troubleshooting guide for CLI, document, issue, or sync errors
Checklist
Copy this checklist and track your progress:
- Verify gh CLI is installed and authenticated
- Review edge cases relevant to current operation
- Confirm status-to-label mapping is correct
- Follow lifecycle workflow for end-to-end integration
Reference Documents
| Document | Content |
|---|---|
| op-verify-gh-cli-auth.md | When to Use, Prerequisites, Procedure, Checklist, Examples, Installation Commands, Required Token Scopes, Error Handling, Related Operations |
| edge-cases.md | Issue Already Exists, Design Has No UUID, gh CLI Not Available |
| status-mapping.md | Design Status Values, GitHub Label Mapping, Valid Status Transitions, Label Naming Convention, Automated Label Management, Manual Label Operations |
| troubleshooting.md | gh CLI Errors, Document Errors, Issue Errors, Sync Errors |
| design-lifecycle-workflow.md | Steps, Full Example |
Examples
Example: gh auth status to verify authentication before any GitHub operation
Error Handling
| Issue | Fix |
|---|---|
| gh CLI not found | brew install gh |
| Token expired | gh auth refresh |
| Status label conflict | Remove old labels manually, re-run sync |
Output
| Type | Description |
|---|---|
| Auth verification | Confirmation of gh CLI authentication status |
| Sync result | Labels updated on GitHub issues |
What ships with it
5 files 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.
- 6d ago First seen · 68 lines · 36 tokens per session scan A 8097cbc9be7b
amaa-github-integration-ops is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 8d ago), licensed MIT. It adds 36 tokens to every session and 535 once invoked, about $0.0002 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".