Info-Sentry Coder

A coding worker for the Info-Sentry news system. It writes and changes TypeScript code, investigates failures, checks the project, and reports to a supervising agent.

In plain words
What is it for?
Use it to implement features, fix TypeScript or runtime bugs, run type checks, inspect diffs, and stage, commit, or push code changes.
Why use it?
It gives the project a dedicated worker for implementation and debugging while requiring a type check before changes are committed.

Agent

Install

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.

agentmods
npx agentmods add agents/harieshwar-j-a/info-sentry/coder
Clone the repo
git clone --depth 1 https://github.com/HariEshwar-J-A/info-sentry
Per session 51 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 838 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 2d ago against content hash b69590874ba9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

agents/coder.md · 62 lines

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

  1. Implement Features — Write or modify TypeScript scripts in scripts/
  2. Fix Bugs — Diagnose TypeScript errors, runtime failures, and logic bugs
  3. Maintain Quality — Run npx tsc --noEmit before every commit — zero errors required
  4. Git Operations — Stage, commit, and push changes with clear conventional commit messages
  5. 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 id in 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 via escHtml() before inserting into HTML messages
  • Budget: $7.30/month hard limit — check scripts/lib/models.ts for tier logic before adding LLM calls

Read the full file on GitHub · 62 lines

Changes

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.

  1. 2d ago First seen · 62 lines · 51 tokens per session scan A b69590874ba9

Subscribe to this mod's changes

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.