Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Emasoft/ai-maestro-architect-agentnpx agentmods add skills/emasoft/ai-maestro-architect-agent/amaa-github-integrationWrote 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)<a href="https://agentmods.dev/skills/emasoft/ai-maestro-architect-agent/amaa-github-integration"><img src="https://agentmods.dev/badge/skills/emasoft/ai-maestro-architect-agent/amaa-github-integration.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.00029 | $0.00939 |
| Opus 5 | $0.00015 | $0.00469 |
| Sonnet 5 | $0.00006 | $0.00188 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
amaa-github-integration 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Integration Skill
Overview
Link design documents to GitHub issues for complete traceability. Create issues from designs, attach designs to existing issues, and keep status synchronized between design document status and GitHub issue labels.
Prerequisites
- gh CLI installed and authenticated (
gh auth status) - Current directory within a GitHub repository
- Design documents with valid UUID in frontmatter
Instructions
- Verify gh CLI is authenticated:
gh auth status - Verify design document has UUID in frontmatter
- Choose and execute the appropriate operation:
- Create issue:
python scripts/amaa_github_issue_create.py --uuid <UUID> - Attach to issue:
python scripts/amaa_github_attach_document.py --uuid <UUID> --issue <N> - Sync status:
python scripts/amaa_github_sync_status.py --uuid <UUID>
- Create issue:
- Use
--dry-runflag on create to preview before executing - Verify results and confirm design frontmatter was updated
- For batch sync of all linked documents:
--allflag on sync script - Monitor GitHub Project board for external changes (see monitoring ref)
Checklist
Copy this checklist and track your progress:
- Verify gh CLI is installed and authenticated
- Confirm design document has valid UUID in frontmatter
- Choose the correct operation (create, attach, or sync)
- Run with
--dry-runflag to preview before executing - Execute the chosen operation
- Verify design frontmatter was updated with results
- Confirm GitHub issue reflects the expected state
Reference Documents
| Document | Description |
|---|---|
| op-create-issue-from-design.md | When to Use, Prerequisites, Procedure, Checklist, Examples, Error Handling, Related Operations |
| op-attach-design-to-issue.md | When to Use, Prerequisites, Procedure, Checklist, Examples, Error Handling, Related Operations |
| op-sync-status-to-github.md | When to Use, Prerequisites, Procedure, Checklist, Examples, Status to Label Mapping, Error Handling, Related Operations |
| op-monitor-github-project.md | When to Use, Prerequisites, Procedure, [TIMESTAMP], Checklist, Examples, What to Monitor, Error Handling, Related Operations |
| op-generate-design-uuid.md | When to Use, Prerequisites, Procedure, Checklist, Examples, UUID Format, Error Handling, Related Operations |
What ships with it
11 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.
- README.md 1.4 KB
- references/design-lifecycle-workflow.md 1.8 KB
- references/edge-cases.md 2.0 KB
- references/op-attach-design-to-issue.md 3.5 KB
- references/op-create-issue-from-design.md 3.9 KB
- references/op-generate-design-uuid.md 3.6 KB
- references/op-monitor-github-project.md 5.0 KB
- references/op-sync-status-to-github.md 3.6 KB
- references/op-verify-gh-cli-auth.md 4.3 KB
- references/status-mapping.md 5.7 KB
- references/troubleshooting.md 5.9 KB
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 · 90 lines · 29 tokens per session scan A 6494686aa100
amaa-github-integration is a skill published in the GitHub repository Emasoft/ai-maestro-architect-agent (2 stars, last pushed 8d ago), licensed MIT. It adds 29 tokens to every session and 939 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-31.
Other skills, from other repositories
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-sync-helper
General GitHub basic operations + automation for GitHub platform objects (Issues/Labels/Milestones/Releases/Actions) in the Minis environment. This skill must be triggered when the user mentions any basic Git/GitHub operation or workflow, including "how to use GitHub," clone, init, remote, branch, commit, push, pull…