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 Chip-G0202/PaperEcho --skill paperecho-localgit clone --depth 1 https://github.com/Chip-G0202/PaperEchoWrote 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/chip-g0202/paperecho/paperecho-local)<a href="https://agentmods.dev/skills/chip-g0202/paperecho/paperecho-local"><img src="https://agentmods.dev/badge/skills/chip-g0202/paperecho/paperecho-local/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/chip-g0202/paperecho/paperecho-local"><img src="https://agentmods.dev/badge/skills/chip-g0202/paperecho/paperecho-local.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Excessive Agency · line 16 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00051 | $0.01178 |
| Opus 5 | $0.00026 | $0.00589 |
| Sonnet 5 | $0.00010 | $0.00236 |
| Haiku 4.5 | $0.00005 | $0.00118 |
Grade A, and why
paperecho-local 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 12d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PaperEcho - Local
Run the complete local-first literature workflow without representing Local as a Zotero backend. Reuse shared domain services and keep filesystem persistence in the Local adapter.
Execution Intent Routing
- Production intent such as “运行”, “跑一次”, “完整流程”, “文献追踪”, “检查配置并启动”, or “配置完成，继续” must use only
node skills/paperecho-local/scripts/run.mjs. SupplyinputandoutputRootthrough--config config/paperecho.config.jsonor explicit--input/--output-root; with sufficient parameters invoke--run, otherwise invoke only--check. - Development intent such as modifying, fixing, refactoring, auditing code, or updating tests must not invoke the production launcher. Use temporary roots, mocks, and targeted validation.
- Explanation intent must only explain or invoke
--check; never invoke--run. - A reply of “继续” reruns the same launcher with the same
--config, reloads the file, and performs a fresh preflight. Inspect onlycommonpluslocal; do not reuse readiness, wait in the background, inspect Zotero configuration, or switch to Desktop/Web. - Never ask the user to paste secrets into chat. Loading this Skill alone causes no production side effect, and production execution must not modify code or create a Git commit.
Read the shared execution contract before invoking the launcher. It defines profiles, preflight, blocked recovery, current-run validation, exit codes, and secret handling; this Skill fixes the mode to Local and must not choose another launcher.
The launcher-fixed Local mode must agree with an explicit config mode or unique enabled section; a Desktop/Web selection is a blocking conflict. Missing output is grouped into common and local only. state, runs, exports, feedback, and checkpoints derive from outputRoot; do not add separate roots. Use the shared configuration guide.
Architecture Boundary
- Entry:
workflow/tools/local/main.mjs::runLocalPipelineand its CLImain. - Shared: Stage1 classification/learning, literature identity normalization, shared literature index, title translation/cache, and Stage4 workbook mapping.
- Local adapter: import, papers snapshot, feedback JSONL, learning checkpoint, run timings, and export directories.
- Forbidden: Zotero readiness, backend factory, Desktop launcher, Stage2, Stage3, itemKey, collection, attachment, rating, or Zotero metadata writeback.
- Do not make Local implement
zotero_backend_contract.mjsand do not call the complete Stage3 merely to generate translations. - For shared or cross-path behavior, first use paperecho-workflow and load its relevant reference.
What ships with it
4 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.
- 12d ago First seen · 62 lines · 51 tokens per session scan A 4af23160d4bc
paperecho-local is a skill published in the GitHub repository Chip-G0202/PaperEcho (56 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,178 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-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…