Borrowing it
Nothing to install: this file belongs to aget-framework/aget. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/aget-framework/aget/main/.claude/skills/aget-document-finding/SKILL.mdgit clone --depth 1 https://github.com/aget-framework/agetWrote 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/aget-framework/aget/aget-document-finding)<a href="https://agentmods.dev/skills/aget-framework/aget/aget-document-finding"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-document-finding/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/aget-framework/aget/aget-document-finding"><img src="https://agentmods.dev/badge/skills/aget-framework/aget/aget-document-finding.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.00010 | $0.00599 |
| Opus 5.5 | $0.00004 | $0.00240 |
| Sonnet 5.5 | $0.00002 | $0.00120 |
| Haiku 4.5 | $0.00001 | $0.00060 |
Grade A, and why
aget-document-finding 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 1mo 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aget-document-finding
Document research findings with evidence, methodology, and implications. Creates structured finding documents for knowledge capture.
Instructions
When this skill is invoked:
-
Formulate Finding
- Clear, specific statement
- Falsifiable where possible
- Scoped appropriately
-
Document Evidence
- Primary sources
- Data/observations
- Chain of reasoning
-
Describe Methodology
- How finding was reached
- Tools/techniques used
- Reproducibility notes
-
Articulate Implications
- What this means
- Recommended actions
- Future research directions
-
Note Limitations
- Scope boundaries
- Confidence level
- Known gaps
Output Format
# Research Finding: [Title]
**Date**: [YYYY-MM-DD]
**Researcher**: [Agent Name]
**Status**: [Draft/Reviewed/Accepted]
**Confidence**: [High/Medium/Low]
---
## Finding Statement
[Clear, specific, falsifiable statement of what was discovered]
---
## Evidence
### Primary Sources
1. [Source 1]: [What it shows]
2. [Source 2]: [What it shows]
### Data/Observations
- [Observation 1]
- [Observation 2]
### Reasoning Chain
1. [Premise 1]
2. [Premise 2]
3. Therefore: [Conclusion]
---
## Methodology
**Approach**: [Description of method]
**Tools Used**:
- [Tool 1]
- [Tool 2]
**Reproducibility**: [How to reproduce this finding]
---
## Implications
### Immediate
- [Implication 1]
### Strategic
- [Longer-term implication]
### Recommended Actions
1. [Action 1]
2. [Action 2]
---
## Limitations
1. [Limitation 1]: [How it affects conclusions]
2. [Limitation 2]: [How it affects conclusions]
---
## Future Research
- [Question raised by this finding]
---
## References
1. [Citation 1]
Constraints
- C1: NEVER document findings without evidence — findings must be supported
- C2: NEVER overstate confidence level — epistemic humility required
- C3: NEVER omit contradictory evidence — complete picture enables sound judgment
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.
- 1mo ago First seen · 134 lines · 10 tokens per session scan A 9b028ca41e09
aget-document-finding is a skill published in the GitHub repository aget-framework/aget (12 stars, last pushed 7d ago), licensed Apache-2.0. It adds 10 tokens to every session and 599 once invoked, about $0.0000 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.
Other skills, from other repositories
aget-create-briefing
Generate standalone narrative documents from session artifacts, optimized for a target consumption medium (NotebookLM, slides, memo, share-draft). Use when the user says "create briefing", "create a briefing for NotebookLM", "make this listenable", "summarize session for [medium]", "prepare a listen", "brief me on…
aget-check-kb
Validate Knowledge Base health by checking structure, frontmatter compliance, and content staleness. Returns conformance score and health status (OK/WARN/CRITICAL).
aget-close-project
Close a PROJECTPLAN with verifiable-assertion gate (V-tests + commits + retrospective), deferred-surface scan for next-plan handoff, and status transition (ACTIVE → COMPLETE / CLOSED / ABANDONED / SUPERSEDED). Strict counterpart to /aget-create-project (D71 Layer 2). Closes asymmetric verb-pair gap at PROJECTPLAN…
aget-release-critique
Adversarial review with the Critic perspective of the Release Delivery Triad (L818). Dual mandate — spec coverage audit plus deep bug finding, asking what breaks in the field and which assumptions are wrong. Superseded by /aget-check-release.
aget-release-audit-specs
Audit specifications with the Spec Auditor perspective of the Release Delivery Triad (L818) — coverage and consistency mode, asking whether a spec covers all behaviors and where gaps or contradictions remain. Superseded by /aget-check-release.
aget-release-build
Execute release gate deliverables with the Builder perspective of the Release Delivery Triad (L818) — speed-optimized execution asking whether the work is done, fast, and functional. Superseded by /aget-create-release.