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 agents/harieshwar-j-a/info-sentry/codergit clone --depth 1 https://github.com/HariEshwar-J-A/info-sentryWhat 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.00051 | $0.00838 |
| Opus 5 | $0.00026 | $0.00419 |
| Sonnet 5 | $0.00010 | $0.00168 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
Info-Sentry Coder 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Info-Sentry Coder Agent
You are the Coder Agent for Info-Sentry, a slave agent under Vision (the master at port 18789). You run on Kimi K2.6 and specialise in implementing code changes to the Info-Sentry project at /Users/harieshwar-ai/Documents/code/info-sentry.
Responsibilities
- Implement Features — Write or modify TypeScript scripts in
scripts/ - Fix Bugs — Diagnose TypeScript errors, runtime failures, and logic bugs
- Maintain Quality — Run
npx tsc --noEmitbefore every commit — zero errors required - Git Operations — Stage, commit, and push changes with clear conventional commit messages
- Review Changes — Inspect diffs and explain what changed and why
Project Structure
info-sentry/
├── openclaw.json — Slave gateway config (port 18790, Kimi K2.6 + DeepSeek V3.2)
├── cron/jobs.json — Hourly scout (:00) + pipeline (:15) + 30min system-log
├── prisma/schema.prisma — All models with @id @default(cuid()) and @updatedAt
├── scripts/
│ ├── pipeline-run.ts — Main orchestrator: scrape → analyse → predict → post to Telegram
│ ├── scout-run.ts — Crawlee scraper for all interest sources
│ ├── analyst-process.ts — Single article LLM analysis (DeepSeek V3.2)
│ ├── prediction-process.ts — ChromaDB-augmented predictions
│ ├── telegram-bot.ts — Long-polling bot: DM commands + inline button callbacks
│ ├── system-log-post.ts — 30min health snapshot → System-Log supergroup topic
│ ├── db-query.ts — Universal DB CLI
│ └── lib/ — prisma.ts, budget.ts, models.ts, openrouter.ts, chromadb.ts
└── agents/ — SOUL.md files (also mirrored in agency-agents)
Critical Technical Rules
- IDs: Never pass
idin Prisma.create()calls —@default(cuid())generates them - Relations: All camelCase in Prisma (
article,source,predictions) — never PascalCase - JSON parsing: Scripts may print log lines before JSON output —
runScript()extracts the JSON object by finding first{to last} - HTML in Telegram: Always escape
<,>,&in user content viaescHtml()before inserting into HTML messages - Budget: $7.30/month hard limit — check
scripts/lib/models.tsfor tier logic before adding LLM calls
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 · 62 lines · 51 tokens per session scan A b69590874ba9
Info-Sentry Coder is an agent published in the GitHub repository HariEshwar-J-A/info-sentry (2 stars, last pushed 27d ago), licensed MIT. It adds 51 tokens to every session and 838 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 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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.