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/jmagly/aiwgnpx agentmods add skills/jmagly/aiwg/prefill-cardsWrote 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/jmagly/aiwg/prefill-cards)<a href="https://agentmods.dev/skills/jmagly/aiwg/prefill-cards"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/prefill-cards/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/jmagly/aiwg/prefill-cards"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/prefill-cards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00020 | $0.01188 |
| Opus 5 | $0.00010 | $0.00594 |
| Sonnet 5 | $0.00004 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
prefill-cards 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 9d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill access pattern (post-kernel-pivot, 2026.5+)
Skill names referenced in this document are AIWG skills, not slash commands. Most are not kernel-listed and cannot be invoked as
/skill-nameby the platform. Reach them via:aiwg discover "<capability>" aiwg show skill <name>Only kernel-listed skills (
aiwg-doctor,aiwg-refresh,aiwg-status,aiwg-help,use,steward) are directly invokable as slash commands. See skill-discovery rule.
Prefill Cards
You auto-populate SDLC artifact metadata headers across all templates in the current project using team configuration from .aiwg/team/team-profile.md.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "stamp the templates" → prefill all artifact headers
- "fill in the authors" → populate author fields from team profile
- "our team just onboarded" → run prefill after team setup
- "set up the project metadata" → prefill cards with project info
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Prefill request | "prefill cards" | Run aiwg prefill-cards |
| Populate request | "populate metadata" | Run aiwg prefill-cards |
| Fill templates | "fill sdlc cards" | Run aiwg prefill-cards |
| Auto-populate | "auto-populate artifacts" | Run aiwg prefill-cards |
| Dry run | "show what prefill would change" | Run aiwg prefill-cards --dry-run |
| Specific type | "prefill just the use case cards" | Run aiwg prefill-cards --type use-cases |
Behavior
When triggered:
-
Extract intent:
- Is this a dry run (preview) or should changes be written?
- Is a specific artifact type mentioned (use cases, ADRs, test plans)?
- Has the user indicated a specific author or date override?
-
Run the appropriate command:
# Default: prefill all artifact templates aiwg prefill-cards # Preview only — show what would change aiwg prefill-cards --dry-run # Limit to a specific artifact type aiwg prefill-cards --type use-cases aiwg prefill-cards --type adrs aiwg prefill-cards --type test-plans # Override author (useful when project lead differs from default) aiwg prefill-cards --author "Jane Smith"
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.
- 9d ago First seen · 140 lines · 20 tokens per session scan A 347598f6f79d
prefill-cards is a skill published in the GitHub repository jmagly/aiwg (211 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 1,188 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-09-03.
Other skills, from other repositories
state
Use when the user says 'update state', 'project state', 'where was I', or at session start to load current context.
gstack-sprint
3-Phase Sprint workflow — design → execute → review with user interaction at decision points.
dos-dispatch
Plan and ship the next batch on one lane: run dos-next-up, acquire a lease with dos arbitrate, gate empty work, dispatch the packet, and archive the run. Use when a single lane should move end to end with collision safety.
dos-class-cycle
Run one DOS plan-class lifecycle tick from the workspace [lifecycle] table: evaluate declared transitions, have a judge approve/defer them, write gated plan-meta edits, and log the cycle. Use when gardening plan lifecycle classes automatically.
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
task-copilot
Use when work should be tracked with tc, including creating PRDs, tasks, handoffs, logs, and work products, or when preserving detailed outputs outside the chat context.