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.
git clone --depth 1 https://github.com/sjungling/sjungling-claude-pluginsWrote 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/agents/sjungling/sjungling-claude-plugins/swift-lint)<a href="https://agentmods.dev/agents/sjungling/sjungling-claude-plugins/swift-lint"><img src="https://agentmods.dev/badge/agents/sjungling/sjungling-claude-plugins/swift-lint/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/agents/sjungling/sjungling-claude-plugins/swift-lint"><img src="https://agentmods.dev/badge/agents/sjungling/sjungling-claude-plugins/swift-lint.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.00035 | $0.00405 |
| Opus 5 | $0.00017 | $0.00202 |
| Sonnet 5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
swift-lint 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.
What it actually says
Format and lint Swift code for the target project. The dispatching command will provide context including the plugin root path and target path.
Step 1: Run swift-lint.sh
Execute the helper script which handles periphery (auto-detected), formatting, and linting in a single invocation:
bash <plugin-root>/commands/references/swift-lint.sh [path] --periphery
- Pass the target path (or
.for the full project) - Always pass
--periphery— the script automatically skips if periphery is not installed or the project lacks configuration - The
<plugin-root>path will be provided by the dispatching command
The script outputs one JSON line per step with the structure: {"step": "...", "status": "...", "output": "..."}.
Step 2: Handle Results
Parse the JSON output from the script:
- periphery step (if run): Note any unused code findings
- format step: Note that formatting was applied in-place
- lint step:
- If
statusis"clean"— done - If
statusis"issues"— read the flagged files, fix each lint issue using Edit, then re-verify by running:bash <plugin-root>/commands/references/swift-lint.sh [path] --lint-only - Repeat until lint is clean
- If
Step 3: Report Summary
Provide a concise summary including:
- Number of files formatted
- Number of lint issues found and fixed
- Any unused code findings from periphery
- Whether lint is now clean
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 · 46 lines · 35 tokens per session scan A 982cff45e578
swift-lint is an agent published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 27d ago), licensed MIT. It adds 35 tokens to every session and 405 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.