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 agentmods add skills/pilinux/gorest/file-readernpx skills add pilinux/gorest --skill file-readergit clone --depth 1 https://github.com/pilinux/gorestWrote 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/pilinux/gorest/file-reader)<a href="https://agentmods.dev/skills/pilinux/gorest/file-reader"><img src="https://agentmods.dev/badge/skills/pilinux/gorest/file-reader.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 | $0.00023 | $0.00225 |
| Opus 5 | $0.00012 | $0.00112 |
| Sonnet 5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
file-reader 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 5d 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
File Reader
When to Use
- User requests exact lines, signatures, constants, or a short factual summary of a specific file or function.
Responsibilities
- Read only the minimum necessary lines and provide
path:linecitations. - Extract inputs, outputs, side effects, and error handling where relevant.
Rules
- Do not modify files or run shell commands.
- Prefer targeted reads over whole-file dumps.
Output
- 2-6 sentence summary.
- Minimal code snippets (only necessary lines) with
path:line. - Suggested follow-ups (1-2 paths).
Examples
- "Show the password hashing implementation in
lib/with exact lines." - "What does
model.Authlook like including struct tags?"
Related Skills
explain-code(synthesis),code-navigation(locate files)
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.
- 5d ago First seen · 40 lines · 23 tokens per session scan A 76eb2474aeeb
file-reader is a skill published in the GitHub repository pilinux/gorest (504 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 225 once invoked, about $0.0001 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 skills, from other repositories
golang
Use when building Go backend services, implementing goroutines/channels, handling errors idiomatically, writing tests with testify, or following Go best practices for APIs/CLI tools.
golang-backend-development
Complete guide for Go backend development including concurrency patterns, web servers, database integration, microservices, and production deployment.
software-engineer-go
Auto-route to this skill if project contains.
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
migrate-goldmark-app-v1-to-v2
Migrate your application from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.