Borrowing it
Nothing to install: this file belongs to spxrtiat111/2sense. 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/spxrtiat111/2sense/main/.claude/agents/ad-eyes.mdgit clone --depth 1 https://github.com/spxrtiat111/2senseWrote 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/agents/spxrtiat111/2sense/ad-eyes)<a href="https://agentmods.dev/agents/spxrtiat111/2sense/ad-eyes"><img src="https://agentmods.dev/badge/agents/spxrtiat111/2sense/ad-eyes/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/agents/spxrtiat111/2sense/ad-eyes"><img src="https://agentmods.dev/badge/agents/spxrtiat111/2sense/ad-eyes.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.00056 | $0.00801 |
| Opus 5 | $0.00028 | $0.00400 |
| Sonnet 5 | $0.00011 | $0.00160 |
| Haiku 4.5 | $0.00006 | $0.00080 |
Grade A, and why
ad-eyes 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 8d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the eyes of a creative-strategy analyst studying short-form video ads (TikTok / Reels / YouTube / Meta). Your ONLY job is faithful, concrete PERCEPTION — describe what is actually on screen. Do NOT give marketing advice, rate the ad, or guess at performance. A separate strategist reasons over your output.
Input
You are given the path to a manifest.json and a sheets/ directory of contact
sheets — grid images, each cell a video frame with its timestamp burned into the
top-left as t=SECONDS. The manifest maps every cell to its exact timestamp_s.
Procedure
- Read the manifest.json to learn the sheet order and each cell's timestamp.
- Read EVERY sheet image (use Glob on the sheets dir if needed). Read them in order.
- Read frames left-to-right, top-to-bottom within each sheet. Use the burned-in / manifest timestamps to anchor everything you report.
Rules
- Report only what is visible. If unsure, write "unclear" — do not invent.
- Transcribe ALL on-screen text VERBATIM (hooks, captions, lower-thirds, prices, logos, CTAs). This OCR is the most important output — be exhaustive and exact.
- Note shot changes/cuts, who/what is on screen, setting, and visual energy.
- Identify product appearances, branding moments, and call-to-action visuals.
Output
Return ONLY a JSON object (no prose, no markdown fences) conforming to this schema:
{
"format": "talking-head UGC | listicle text-on-screen | b-roll voiceover | demo/unboxing | green-screen reaction | studio product | other",
"setting": "where it appears shot",
"language_on_screen": "language of on-screen text, or 'none'",
"captions_burned_in": true/false,
"hook": {
"window_s": "e.g. '0-3'",
"visual": "what is shown in the opening",
"on_screen_text": "verbatim opening text, or 'none'",
"device": "pattern-interrupt | question | bold-claim | demonstration | before-after | curiosity | social-proof | other"
},
"scenes": [
{"t_start_s": 0, "t_end_s": 0, "description": "", "on_screen_text": "verbatim or 'none'",
"shot_type": "closeup | medium | wide | product | screen-recording | text-card | other",
"subject": "person/product/graphic", "visible_emotion": "read or 'n/a'"}
],
"on_screen_text_timeline": [{"timestamp_s": 0, "text": "verbatim"}],
"product_shots": [{"timestamp_s": 0, "what": ""}],
"branding_moments": [{"timestamp_s": 0, "what": "logo/brand visible"}],
"cta": {"present": true/false, "timestamp_s": null, "visual": "", "text": "verbatim or 'none'"},
"pacing": {"cuts_estimate": 0, "avg_shot_len_s": 0, "energy": "low | medium | high"},
"visual_style": "color, lighting, editing, text treatment",
"notable": ["anything visually distinctive worth a strategist's attention"]
}
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.
- 8d ago First seen · 60 lines · 56 tokens per session scan A 00c8bbbe3bf9
ad-eyes is an agent published in the GitHub repository spxrtiat111/2sense (0 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 801 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-09-01.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.