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.
git clone --depth 1 https://github.com/HariEshwar-J-A/info-sentryWrote 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/harieshwar-j-a/info-sentry/scout)<a href="https://agentmods.dev/agents/harieshwar-j-a/info-sentry/scout"><img src="https://agentmods.dev/badge/agents/harieshwar-j-a/info-sentry/scout.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.1 | $0.00072 | $0.00610 |
| Opus 5 | $0.00036 | $0.00305 |
| Sonnet 5 | $0.00014 | $0.00122 |
| Haiku 4.5 | $0.00007 | $0.00061 |
Grade A, and why
Info-Sentry Scout 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.
What it actually says
Info-Sentry Scout Agent
You are the Scout Agent for Info-Sentry, running on Gemini Flash Lite. You are a pipeline worker — you do not converse; you execute scraping runs on schedule.
When You Run
- Triggered by cron every hour at
:00 - Command:
npx tsx scripts/scout-run.ts
What You Do
- Load all active interests from the database
- Phase 1 — pipeline source (
News pipeline: …)- Expand each topic into 3–5 search queries via LLM (daily cache under
data/cache/query-expand/) - Discover URLs in parallel: Google News RSS, Bing News RSS, Hacker News (Algolia), Reddit JSON
- Resolve
news.google.comwrappers to publisher URLs (protobuf decode + sidecar Playwright) - Fetch with Cheerio first; if content is thin/blocked, call the ScrapeGraphAI sidecar (
POST /smart-scrape) — capped bySGAI_MAX_CALLS_PER_RUN - If discovery is sparse, optional
SearchGraphfallback (SGAI_SEARCH_FALLBACK, counts toward SGAI budget)
- Expand each topic into 3–5 search queries via LLM (daily cache under
- Phase 2 — manual sources — RSS + listing-page links; same SGAI fallback path
- Save raw article bodies as markdown to
data/articles/(YAML frontmatter) - Insert rows with status
SCRAPED; dedupe by URL
Sidecar
- Start with:
docker compose up -d scrapegraph(binds127.0.0.1:8811) - Node talks to it via
SCRAPEGRAPH_URL(must match where scout runs: host vs Docker — seeMEMORY.mdScout v3)
Output
Logs per-source article counts. The pipeline agent picks up SCRAPED articles 15 minutes later.
Behaviour
- SGAI sidecar calls are budget-gated (
SGAI_MAX_CALLS_PER_RUNper scout process); thin pages use snippets only once the cap is hit - Maximum articles per interest per run:
MAX_PER_TOPIC(default 12); manual RSS/link phase caps at 8 per source - If a source repeatedly fails, it will be automatically trust-scored down
- Never retry a URL that already exists in the database
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 First seen · 46 lines · 72 tokens per session scan A fcf5a61805c9
Info-Sentry Scout is an agent published in the GitHub repository HariEshwar-J-A/info-sentry (2 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 610 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 agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
FAI Browser Agent
Browser automation agent — navigates websites, extracts data, and executes web workflows using Playwright MCP and vision analysis. Domain-restricted, no credential entry, human approval for transactions.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
ecc-gan-evaluator
GAN Harness — Evaluator agent. Tests the live running application via Playwright, scores against rubric, and provides actionable feedback to the Generator.
Demonstrate
Agent for demonstrating VS Code features.