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 existential-birds/beagle --skill artifact-analysisgit clone --depth 1 https://github.com/existential-birds/beagleWrote 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/existential-birds/beagle/artifact-analysis)<a href="https://agentmods.dev/skills/existential-birds/beagle/artifact-analysis"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/artifact-analysis/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/existential-birds/beagle/artifact-analysis"><img src="https://agentmods.dev/badge/skills/existential-birds/beagle/artifact-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Data Exfiltration · line 3 Code or instructions that leak agent conversation context to external services, potentially exposing sensitive user interactions.Fix: Remove any code that sends prompts, responses, or session data externally. Preserve user privacy; never exfiltrate conversation content.
- medium Agent Snooping · line 23 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00192 | $0.03902 |
| Opus 5.5 | $0.00077 | $0.01561 |
| Sonnet 5.5 | $0.00038 | $0.00780 |
| Haiku 4.5 | $0.00019 | $0.00390 |
Grade A, and why
artifact-analysis 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 2mo 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Artifact Analysis
Turn a set of local paths (or a beagle project's conventional knowledge locations) into a cited, structured extraction of insights, context, decisions, and raw detail.
The deliverable is always on disk: a written scan plan the caller can audit, one findings file per slice, and a synthesized report with path-anchored citations. Nothing returns as inline prose, and no claim ships without a source path + verbatim excerpt behind it.
When to use
- A user asks for a local-document read — "analyze the docs folder", "scan the project for context", "extract what's in .beagle/concepts/".
- Another beagle skill invokes this one programmatically as a grounding companion (see
references/companion-contract.md). - The caller wants auditable output: a plan written before extraction, findings files per slice, and a citation-backed synthesis report.
When NOT to use
- Codebase lookups ("where is this function defined", "grep for this symbol"). Search the codebase instead.
- Web research. Use web-research.
- Comparative evaluation of two implementations or source credibility adjudication. Use llm-judge.
- Rewriting or editing the scanned documents. Use humanize-beagle (../../../beagle-docs/skills/humanize-beagle/SKILL.md) or edit the files directly.
- PDF / image OCR / format conversion. First version reads plain text and markdown only.
- Paywalled or authentication-gated remote sources. This is a local-filesystem primitive.
- Coaching, challenge, or reshaping of the caller's question. That belongs to the caller.
Workflow
Four steps, in order. No step is skippable.
Hard gates
Advance to the next step only when the pass condition is true—confirm using files under output_dir (and tool output), not memory.
| After | Pass condition |
|---|---|
plan.md written |
plan.md exists and includes intent, resolved paths, slices, per-slice briefs, skip patterns, budgets applied, and synthesis approach (same fields as The scan plan (plan.md)). |
| Subagent dispatch | Either the empty corpus path was taken (no subagents; plan.md documents zero readable documents) or every slice listed in plan.md has findings/<slice-slug>.md on disk. |
report.md written |
report.md exists; headings match references/report-template.md (seven sections plus ## Sources). |
| Before return to caller | Every row of references/failure-modes.md → Verification checklist (orchestrator runs at end) is checked off, or any failed check is recorded under ## Gaps & Limitations in report.md as that failure-modes file prescribes. |
What ships with it
6 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.
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.
- 2mo ago First seen · 232 lines · 192 tokens per session scan A 93655bf571cc
artifact-analysis is a skill published in the GitHub repository existential-birds/beagle (85 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 192 tokens to every session and 3,902 once invoked, about $0.0008 per session on Opus 5.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.
artifact-analysis compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| artifact-analysisexistential-birds/beagle | Skill | 85 | 1mo ago | Apache-2.0 | A | 192 | Claude Code |
| fsl-requirements-documentymm-oss/fsl | Skill | 37 | yesterday | Apache-2.0 | A | 145 | Claude Code, Codex |
| coding-standardsSimon-Hwang/gg-plugins | Skill | 2 | 3mo ago | none | A | 34 | Claude Code |
| codex-rule-routerSimon-Hwang/gg-plugins | Skill | 2 | 3mo ago | none | A | 39 | Claude Code |
| format-specific-extractionxberg-io/xberg | Skill | 9.5k | yesterday | MIT | A | 15 | Claude Code |
| typescript-providersComposioHQ/composio | Skill | 31k | yesterday | MIT | A | 73 | Claude Code, Codex |
| pr-to-go-lintergithub/gh-aw | Skill | 5.6k | yesterday | MIT | A | 22 | Claude Code, Codex |