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 chrisgagne/grounded-forge --skill audit-attributiongit clone --depth 1 https://github.com/chrisgagne/grounded-forgeWrote 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/chrisgagne/grounded-forge/audit-attribution)<a href="https://agentmods.dev/skills/chrisgagne/grounded-forge/audit-attribution"><img src="https://agentmods.dev/badge/skills/chrisgagne/grounded-forge/audit-attribution.svg" alt="Measured on agentmods" 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.00060 | $0.03637 |
| Opus 5 | $0.00030 | $0.01818 |
| Sonnet 5 | $0.00012 | $0.00727 |
| Haiku 4.5 | $0.00006 | $0.00364 |
Grade A, and why
audit-attribution 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 8d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit attribution
Run an essay or draft through the library to surface under-attribution: the gap between an essay properly citing sources and an essay where a careful reader can tell what's being built on versus what's being contributed. Citation count is not the metric; the metric is whether the build/contribute boundary is visible from the text alone.
Why this skill exists
When synthesising across multiple bodies of work, an author can produce an essay that:
- Properly cites individual sources, and
- Reproduces the structure, catalogue, or argumentative shape of one source closely enough that a reader of that source recognises it as the same territory, but
- Frames the synthesis as the author's own without naming the closest neighbours in the lineage.
This is not plagiarism—citations exist—but it is under-attribution: the reader can't tell from the text alone what the author is building on versus contributing. The fix is provenance markers that make the build/contribute boundary visible.
A 30-citation essay can still under-attribute. Citation breadth is not citation depth.
When to use
- Sanity-checking a draft before publication (blog post, paper, book chapter, board paper).
- After heavy revision where multiple sources have been integrated and the author's distinctive contribution may have been buried among attributions.
- When the audience includes readers familiar with one or more of the source bodies of work: they're the readers most likely to feel the under-attribution.
When not to use
- Light editorial polish: this skill is heavyweight, designed for substantive synthesis work.
- Fact-checking individual claims against the corpus: that's
answer-from-corpuswith an audit framing, not this skill. - First-draft generation: this is a late-stage check, not a generation tool.
Procedure
Step 1: Read the essay and identify load-bearing contributions
Read the essay in full. Identify:
- The 1-3 distinctive claims the author is contributing. The synthesis is usually one or two specific claims, not the whole essay. Surface these explicitly before any neighbour scan: buried distinctive claims are a separate failure mode (silent demotion) that the audit must flag.
- The named coinages in the essay: capitalised phrases, in-quotes terms, idiosyncratic vocabulary that may be someone else's. Examples: "Poetic Attunement", "Inherent Simplicity", "Self-Improvement Trap", "Lethal Paradigm", "Build/Contribute Boundary".
- The argument's shape: section logic, what it catalogues, what it prescribes, the diagnosis-prescription arc.
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.
- 8d ago First seen · 226 lines · 0 tokens per session scan A 3dd79b75f789
audit-attribution is a skill published in the GitHub repository chrisgagne/grounded-forge (7 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 3,637 once invoked, about $0.0003 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
warpp-workflow-authoring
Author WARPP workflows for Manifold as typed-port dataflow JSON. Use when a user asks to build, create, design, generate, or edit a Flow / workflow / automation / pipeline / DAG in Manifold, or mentions WARPP, workflow nodes, or the /flow builder. Covers the document format, port types and coercions, the builtin node…
manifold-api
Use when an agent needs to inspect or call the local Manifold HTTP API. Provides guidelines and scripts to filter specs before reading and handle payloads safely.
duckduckgo-search
Free keyless web, news, and image search via ddgs.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…