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 hutzelmann/thesis-proposal-skills --skill proposal-lit-searchgit clone --depth 1 https://github.com/hutzelmann/thesis-proposal-skillsWrote 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/hutzelmann/thesis-proposal-skills/proposal-lit-search)<a href="https://agentmods.dev/skills/hutzelmann/thesis-proposal-skills/proposal-lit-search"><img src="https://agentmods.dev/badge/skills/hutzelmann/thesis-proposal-skills/proposal-lit-search/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/hutzelmann/thesis-proposal-skills/proposal-lit-search"><img src="https://agentmods.dev/badge/skills/hutzelmann/thesis-proposal-skills/proposal-lit-search.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 Rogue Agent · line 12 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00081 | $0.01735 |
| Opus 5 | $0.00041 | $0.00868 |
| Sonnet 5 | $0.00016 | $0.00347 |
| Haiku 4.5 | $0.00008 | $0.00173 |
Grade A, and why
proposal-lit-search 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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Literature Search
Finds sources for a topic or a draft and merges the accepted entries into the proposal's references: block as CSL-YAML — keyword search across public scholarly databases, plus snowballing from what is already cited.
Workflow: proposal-ideate → proposal-lit-search → proposal-write → proposal-check → proposal-review → proposal-publish. Also: proposal-import (start from an existing document), proposal-reverse (derive a proposal from a finished thesis), proposal-customize (adapt the rules to a supervisor's requirements), proposal-supervise (supervisor-side feedback on a raw submission), proposal-troubleshoot (diagnose a skill that misbehaved).
Voice: neutral and constructive — never praise the user or their material, never compliment your own output. Chat messages stay short and precise; findings are stated plainly, with the next step when one exists.
Academic literature only. You judge relevance — the scripts only gather candidates. Peer-reviewed venues beat preprints when both versions exist; vendor/commercial pages are never acceptable sources.
Execution shape
One search, one judge, one merge: the scripts — or, when script networking is denied, your own read-only requests — gather the candidates, and you judge the whole set together and merge the accepted entries yourself, in this one context — never one helper agent per candidate, per source, or per research question, because a preprint and its published version are recognised only side by side, key uniqueness is a property of the whole references block, and the proposal and the notes file have one writer.
Modes
Keyword search (topic or full proposal as context):
python3 ${CLAUDE_SKILL_DIR}/scripts/search.py "distributed consensus energy efficiency" --limit 10
${CLAUDE_SKILL_DIR} is substituted by the host with this skill's install directory; on a host that leaves it unexpanded, the script really lives in scripts/ next to this SKILL.md, so use that path — but keep running the command from the working directory, where api-keys.env is looked up: the fallback changes where the script is found, never where you work. If you cannot find it, say the script did not run and name what is therefore unverified — never present your own reading of the file as the script's result.
What ships with it
10 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.
- evals/evals.json 707 B
- scripts/arxiv.py 2.4 KB runs code
- scripts/common.py 9.4 KB runs code
- scripts/crossref.py 4.5 KB runs code
- scripts/dblp.py 2.5 KB runs code
- scripts/openalex.py 4.0 KB runs code
- scripts/opencitations.py 2.8 KB runs code
- scripts/search.py 2.4 KB runs code
- scripts/semantic_scholar.py 3.9 KB runs code
- scripts/snowball.py 3.4 KB runs code
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.
- 7d ago Changed · +4 lines 8d897ac42d97
- 11d ago First seen · 61 lines · 81 tokens per session scan A e0bb34b3a4d5
proposal-lit-search is a skill published in the GitHub repository hutzelmann/thesis-proposal-skills (7 stars, last pushed 8d ago), licensed MIT. It adds 81 tokens to every session and 1,735 once invoked, about $0.0004 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
lore
SpecStory Lore - mine your SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more) into a persistent corpus, surface your reproducible workflows with corroborated evidence, and interactively forge the chosen ones into skills installed across all your agent harnesses. Use when the user…
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
docs-manage
Manage the Grounded Docs MCP Server documentation index. Covers scraping and indexing documentation from URLs or local files, refreshing existing indexes with changed content, and removing libraries from the index. Use when you need to add, update, or delete indexed documentation.
docs-search
Search and query the Grounded Docs MCP Server documentation index. Covers listing indexed libraries, searching documentation content, and resolving library versions. Use when you need to look up API references, find code examples, or check which documentation is available in the local index.
fetch-url
Fetch a single URL and convert its content to Markdown. Use when you need to read a web page, documentation page, or API reference without indexing it. The content is returned as plain Markdown text on stdout.
backseat-driver-testing
Testing strategies for Calva Backseat Driver MCP tools. Use when: Testing Backseat Driver, validating tool updates, testing structural editing workflows, verifying REPL evaluation with who-tracking, testing shadow-cljs runtime discovery and targeting, testing output log filtering, testing load-file tool, smoke testing…