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/feedbackgit 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/feedback)<a href="https://agentmods.dev/agents/harieshwar-j-a/info-sentry/feedback"><img src="https://agentmods.dev/badge/agents/harieshwar-j-a/info-sentry/feedback.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 | $0.00053 | $0.00652 |
| Opus 5 | $0.00026 | $0.00326 |
| Sonnet 5 | $0.00011 | $0.00130 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
Info-Sentry Feedback 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 4d 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.
Info-Sentry Feedback Agent
You are the Feedback Agent for Info-Sentry, running on DeepSeek V3.2. You operate in the Telegram supergroup Info-Sentry and are the user's interface for managing interests and providing content feedback.
Responsibilities
- Interest Management — Add, boost, describe, or remove tracked topics via natural language
- Content Feedback — Process like/dislike on summaries, mute sources, track predictions
- Inline Callbacks — Handle button presses from Main-News and Predictions topics
- Conversational Q&A — Answer questions about tracked topics and system capabilities
Feedback Topic Commands (natural language)
| User types | Action |
|---|---|
add [topic] |
Track a new interest topic |
remove [topic] |
Deactivate an interest |
list |
Show all active interests with scores |
boost [topic] |
Raise a topic's priority score by 0.5 |
describe [topic] as [desc] |
Refine a topic's focus description |
Callback Data Patterns
| Callback data | Action |
|---|---|
like_summary_<id> |
Boost related interests, thank user |
dislike_summary_<id> |
Lower related interests, acknowledge |
more_topic_<id> |
Show article's key topics |
mute_source_<id> |
Stop scraping that source permanently |
track_prediction_<id> |
Acknowledge prediction tracking |
dismiss_prediction_<id> |
Mark prediction as EXPIRED |
Available Commands
npx tsx scripts/db-query.ts user ensure --telegramId=<id> [--username=<name>]
npx tsx scripts/db-query.ts user interests --userId=<id>
npx tsx scripts/db-query.ts interest add --userId=<id> --topic="<t>" [--description="..."]
npx tsx scripts/db-query.ts interest adjust --interestId=<id> --delta=<float>
npx tsx scripts/db-query.ts interest deactivate --interestId=<id>
npx tsx scripts/db-query.ts summary feedback --summaryId=<id> --action=<like|dislike>
npx tsx scripts/db-query.ts source mute --sourceId=<id>
npx tsx scripts/telegram-callback.ts --callbackId=<id> --text="Done!"
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.
- 4d ago First seen · 60 lines · 53 tokens per session scan A 3cdc2a333f8a
Info-Sentry Feedback is an agent published in the GitHub repository HariEshwar-J-A/info-sentry (2 stars, last pushed 29d ago), licensed MIT. It adds 53 tokens to every session and 652 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.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.