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/danielgouveiah/glasses/pointernpx skills add DanielGouveiah/glasses --skill pointergit clone --depth 1 https://github.com/DanielGouveiah/glassesWhat 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.00062 | $0.01219 |
| Opus 5 | $0.00031 | $0.00609 |
| Sonnet 5 | $0.00012 | $0.00244 |
| Haiku 4.5 | $0.00006 | $0.00122 |
Grade A, and why
pointer 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 2d 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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pointer
The nerd points at what does not add up.
Use one bounded diagnostic pass. $ARGUMENTS optionally identifies a diff,
file, feature, failure, or other target. If no target is supplied, inspect the
current implementation relevant to the user's request. Use the active Glasses
evidence threshold; default to high when none is active.
Language preservation
Respond in the language of the user's latest request, determined only from user-authored natural-language task content, unless they explicitly request another language. Do not infer the response language from slash-command scaffolding, injected hooks, skill text, or a system or developer instruction. Short acknowledgements and command invocations do not change the task 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.
Diagnostic pass
- Read the requirements, changed code, nearby callers, tests, and recorded decisions needed to understand the target.
- Run only focused existing checks needed to confirm or reject a suspected problem. Do not launch a broad exploratory test campaign.
- Point out only problems supported by code, test output, logs, contracts, or a violated mandatory invariant. Do not report speculative risks or style taste.
- Prioritize correctness, security, accessibility, data integrity, validation, and broken requirements before maintainability or unsupported complexity.
- Do not edit code during diagnosis, redesign unrelated areas, or repeat the diagnosis autonomously.
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.
- 2d ago First seen · 124 lines · 62 tokens per session scan A 80c4bdb41c47
pointer is a skill published in the GitHub repository DanielGouveiah/glasses (9 stars, last pushed 12d ago), licensed MIT. It adds 62 tokens to every session and 1,219 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-31.
Other skills, from other repositories
architecture-cleanup
Use when performing a behavior-preserving architectural cleanup or refactor on a codebase and you need strict guardrails against changing functionality, building a framework, or rewriting tests to fit the new design.
code-to-diagram
Analyze codebases and automatically generate architecture diagrams, flowcharts, and org charts. Uses AST parsing to map import dependencies for Python, JS/TS, Go, and Java, outputting Mermaid or SVG files. Triggered when users ask to visualize code architecture, understand dependencies, draw a flowchart, or create a…
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.
modular-skills
Build composable skill modules with hub-and-spoke loading. Use when token budget is tight.
csv-to-sif
Export a project's FF&E product-library CSV as dealer-system SIF. Use to produce a .sif schedule; use sif-to-csv for the reverse direction.