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 swan-gtm/gtm-skills --skill audit-swangit clone --depth 1 https://github.com/swan-gtm/gtm-skillsWrote 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/swan-gtm/gtm-skills/audit-swan)<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/audit-swan"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/audit-swan/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/swan-gtm/gtm-skills/audit-swan"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/audit-swan.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.00043 | $0.01125 |
| Opus 5 | $0.00022 | $0.00562 |
| Sonnet 5 | $0.00009 | $0.00225 |
| Haiku 4.5 | $0.00004 | $0.00112 |
Grade A, and why
audit-swan 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instructions
What this skill checks
Eight structural dimensions. Each is small — most produce 0-2 findings. Process them one at a time, write down the verdict (OK / WARN / FAIL) + a one-line summary, and move on. Do not try to gather all eight dimensions' raw data before reasoning. By the time you reach the report, you should have eight short verdicts in hand, nothing more.
Dimension 1 — Subscription and credits
swan-get-subscription. Check three things:
- Plan tier (FREE / paid).
- Credit balance + recent burn rate. If you don't have burn data in the response, estimate from a small
swan-search-sequencesrecent-activity sample (page 10) — don't pull the full log. - Feature flags vs. what active plays use.
Verdict:
- FAIL: out of credits, or active plays use features not enabled.
- WARN: < 30 days runway.
- OK: comfortable.
One-line summary. Move on.
Dimension 2 — Org knowledge
swan-get-memory for org memory.
Required:
- ≥ 1 ICP segment.
- ≥ 1 persona per primary buying motion.
- Value prop set and non-trivial.
- Target markets defined.
- Competition documented.
Verdict:
- FAIL: ICP missing or value prop empty.
- WARN: any other missing or stale (no update in 90+ days).
- OK: all current.
One-line summary.
Dimension 3 — Senders
swan-get-org-senders (this returns a small list — usually < 10 senders). Per sender, check auth status and capacity headroom.
Verdict:
- FAIL: no working sender, or all senders 100% saturated.
- WARN: any sender 80%+ saturated for > 7 days, or auth-broken channel that a play expects.
- OK: ≥ 1 healthy sender with capacity.
One-line summary.
Dimension 4 — Integrations
For each integration referenced by an active trigger:
- Connected and authorized.
- Last successful sync recent.
If integration is referenced by an active trigger but not connected: FAIL.
Don't enumerate integrations the org doesn't use. One-line summary.
Dimension 5 — Active triggers (gradual)
Pull active triggers, page size 10. For each:
- Required inputs available? (sender connected, list exists, integration present)
- Has it fired ≥ 1 time in 60 days, or is it new?
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 · 151 lines · 43 tokens per session scan A c8b87175a45f
audit-swan is a skill published in the GitHub repository swan-gtm/gtm-skills (150 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,125 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-09-03.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…