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 akka/ai-marketplace --skill issuesgit clone --depth 1 https://github.com/akka/ai-marketplaceWrote 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/akka/ai-marketplace/issues)<a href="https://agentmods.dev/skills/akka/ai-marketplace/issues"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/issues/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/akka/ai-marketplace/issues"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/issues.svg" alt="Reviewed on agentmods" width="80" 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.00023 | $0.01045 |
| Opus 5 | $0.00012 | $0.00522 |
| Sonnet 5 | $0.00005 | $0.00209 |
| Haiku 4.5 | $0.00002 | $0.00104 |
Grade A, and why
issues 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 10d 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
You MUST consider the user input before proceeding (if not empty).
Outline
-
Locate the feature: Call the
akka_sdd_list_specsMCP tool to find features. Verify thattasks.mdexists for the target feature (has_tasksmust be true). Iftasks.mdis missing, instruct the user to run/akka:tasksfirst. Read thetasks.mdcontent from FEATURE_DIR. -
Build the task-ID set: Scan
tasks.mdfor every task line — each starts with- [ ]followed by a task ID matchingTand three digits (e.g.T001). Collect the set of task IDs you are about to process. -
Determine the GitHub repository from the git remote:
git config --get remote.origin.url[!CAUTION] ONLY PROCEED TO THE NEXT STEPS IF THE REMOTE IS A GITHUB URL
-
Fetch existing issues for deduplication: Before creating anything, use the GitHub MCP server's
list_issuestool to find issues that already cover the task IDs from step 2.- Do not pass a
statevalue — omitting it returns both open and closed issues. - Request
perPage: 100to minimize calls. - The tool uses cursor-based pagination: request further pages with the
afterparameter using theendCursorfrom the previous response. - For each issue title, match against the pattern
\bT\d{3}\b(word boundaries soST001andT0010do not false-match). This recognizes titles written asT001 ...,T001: ..., or[T001] .... When it matches one of your task IDs, mark that ID as already having an issue. - Stop paginating as soon as every task ID has been matched, or when there are no more pages. This bounds the number of calls on repos with large issue histories.
- Do not pass a
-
Create issues for tasks that don't have one yet: For each task in
tasks.md:- Strip the leading
- [ ]and any[P]/[US#]markers to recover the task ID and description. Example:- [ ] T001 [P] [US1] Create User model in src/models/user.py→ IDT001, descriptionCreate User model in src/models/user.py. - If the ID is in the "already has an issue" set from step 4: skip it and report
T001 already has an issue, skipping. - Otherwise, use the GitHub MCP server's
issue_writetool to create a new issue in the repository derived from the git remote. Use the canonical title format:
- Strip the leading
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.
- 10d ago First seen · 57 lines · 23 tokens per session scan A defd22e64459
issues is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 1,045 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
gsd-quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
gsd-complete-milestone
Archive completed milestone and prepare for next version.
gsd-quick-batch
Batch several /gsd:quick-shaped tasks together — planned, dispatched, and merged as one run.
gsd-workspace
Manage GSD workspaces — create, list, or remove isolated workspace environments.
gsd-inbox
Triage and review open GitHub issues and PRs against project templates and contribution guidelines.
gsd-pause-work
Create context handoff when pausing work mid-phase.