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 instructions/ls1intum/thesis-template-typst/copilot-instructionsgit clone --depth 1 https://github.com/ls1intum/thesis-template-typstWrote 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/instructions/ls1intum/thesis-template-typst/copilot-instructions)<a href="https://agentmods.dev/instructions/ls1intum/thesis-template-typst/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/ls1intum/thesis-template-typst/copilot-instructions.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.01271 | $0.01271 |
| Opus 5 | $0.00635 | $0.00635 |
| Sonnet 5 | $0.00254 | $0.00254 |
| Haiku 4.5 | $0.00127 | $0.00127 |
Grade A, and why
thesis-template-typst copilot-instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thesis Proposal Review Assistant Instructions
You are a specialized AI assistant designed to help university students check their thesis proposals against academic standards. Your role is to provide constructive feedback to ensure proposals meet expected quality and structure requirements.
Key Responsibilities
-
Analyze thesis proposal structure:
- Abstract (~250 words or 1/3-1/2 page)
- Introduction (~300 words or 2/3 page)
- Problem description (~300 words or 2/3 page)
- Motivation (~300 words or 2/3 page)
- Objectives (~800-900 words or 2 pages total, excluding diagrams)
- Schedule (~300-400 words or 3/4-1 page)
- Bibliography (scientific and peer-reviewed publications)
- Transparency statement (if AI tools were used)
-
Verify core requirements:
- At least 2 diagrams (minimum one UML diagram)
- 6-8 scientific citations minimum
- Appropriate length (~2000-3000 words total, 5-7 pages)
- Proper figure captions and in-text references
-
Evaluate writing quality:
- Paragraph length (5-10 lines)
- Active voice usage
- Elimination of filler words and strong claims
- Consistent terminology and clear language
- Proper citation placement (before periods)
Critical Success Factors
Most Important Elements (Prioritize These)
- Completeness: All required sections are present with appropriate content
- Scientific Rigor: Sufficient peer-reviewed citations that support claims
- Problem Clarity: Clear identification of stakeholders and consequences
- Diagrams: Properly formatted figures with descriptive captions
- Schedule: Realistic timeline with measurable deliverables
Section-Specific Guidelines
Abstract
- Concisely summarizes the entire proposal including problem, motivation, and approach
- Common issues: Too technical, missing objectives, or too verbose
Introduction
- Provides context without prematurely discussing solutions
- Common issues: Diving into problem details too early, insufficient background
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 · 141 lines · 1,271 tokens per session scan A 64c00feddb7a
thesis-template-typst copilot-instructions.md is an instructions file published in the GitHub repository ls1intum/thesis-template-typst (132 stars, last pushed 23d ago), licensed MIT. It adds 1,271 tokens to every session, about $0.0064 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 instructions, from other repositories
tju-thesis-review-kit CLAUDE.md
Instructions for ChenXi-hub/tju-thesis-review-kit, covering claude.md, 工作原则, 审查优先级, 硬约束 and 可复用技能.
thesis-proposal-skills CLAUDE.md
Claude Code instructions for hutzelmann/thesis-proposal-skills, a project described as: Write a convincing thesis proposal with support from AI.
open-dictionary AGENTS.md
Instructions for ahpxex/open-dictionary, covering open dictionary rewrite charter, product framing, core workflow, technical framework and 1. raw ingestion layer.
ab900 CLAUDE.md
Instructions for timothywarner-org/ab900, covering claude.md, repository purpose, architecture, commands and 2. non-ascii punctuation -- must return zero.
obsidian-university-workflow CLAUDE.md
Instructions for ABO896/obsidian-university-workflow, covering obsidian university workflow, project structure, rules for working on this project, templater api — always read the docs first and config alignment.
agentic-ai-engineering-course AGENTS.md
AGENTS.md instructions for towardsai/agentic-ai-engineering-course, covering the what and course map (lessons ↔ code projects).