Borrowing it
Nothing to install: this file belongs to DanielGouveiah/glasses. 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/DanielGouveiah/glasses/main/.agents/skills/homework/SKILL.mdgit clone --depth 1 https://github.com/DanielGouveiah/glassesWrote 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/danielgouveiah/glasses/homework)<a href="https://agentmods.dev/skills/danielgouveiah/glasses/homework"><img src="https://agentmods.dev/badge/skills/danielgouveiah/glasses/homework/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/danielgouveiah/glasses/homework"><img src="https://agentmods.dev/badge/skills/danielgouveiah/glasses/homework.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00090 | $0.02675 |
| Opus 5.5 | $0.00036 | $0.01070 |
| Sonnet 5.5 | $0.00018 | $0.00535 |
| Haiku 4.5 | $0.00009 | $0.00267 |
Grade A, and why
homework 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Homework
The nerd does the homework and brings receipts.
$ARGUMENTS optionally provides a research question or target. Support three
depths. Treat source counts as planning ranges, not proof of completeness:
skim: check a narrow claim with the fewest decisive sources, usually 1-3.study: compare a decision with primary evidence and independent cross-checking, usually 4-10 sources. This is the default.thesis: build an auditable evidence notebook, search for counterevidence, and continue until every decision-changing question is sufficiently supported or explicitly unresolved. Do not substitute a larger source count or longer report for this workflow.
Honor an explicit depth. Infer thesis when the user asks for deep,
comprehensive, exhaustive, or thesis-grade research. Depth controls evidential
work, not response verbosity.
Language preservation
Respond in the language of the user's latest request unless they explicitly request another language. Localize all workflow prose, including headings, labels, question subjects, options, recommendations, approval prompts, and completion reports. Any English examples in this skill specify meaning, not literal output.
Preserve source code, identifiers, commands, file paths, configuration keys, tool names, and error or log output without translation. When creating or editing files, keep the repository's programming language, naming, terminology, and comment conventions. Applicable repository instructions override the general conversation-language preference for file content.
Establish the assignment
Explicit general scope overrides project context. When the user asks to research a topic generally or without applying it to their project, keep the research and recommendation general; do not use the repository, company, or recent conversation as hidden decision criteria. Use local context only when the user requests a project-specific application or it is required by the stated assignment.
What ships with it
1 file 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.
- 1mo ago First seen · 276 lines · 90 tokens per session scan A 3384e26ab838
homework is a skill published in the GitHub repository DanielGouveiah/glasses (10 stars, last pushed 28d ago), licensed MIT. It adds 90 tokens to every session and 2,675 once invoked, about $0.0004 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-31.
Other skills, from other repositories
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
modular-skills
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
product-image-processor
Download, resize, and remove backgrounds from product images at scale. Use when the user asks to "process product images", batch-download images from the schedule, strip backgrounds, or standardize product photos.
plugin-review
Review plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.
site-history
Neighborhood context and history — adjacent uses, architectural character, landmarks, commercial activity, and planned development from an address. Use when the user asks about a site's history or surroundings, "what's around this site", neighborhood character, or nearby planned development.