Borrowing it
Nothing to install: this file belongs to Sandeeprdy1729/timps. 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/Sandeeprdy1729/timps/main/.github/agents/daily-improve-agent.agent.mdgit clone --depth 1 https://github.com/Sandeeprdy1729/timpsWrote 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/sandeeprdy1729/timps/daily-improve-agent)<a href="https://agentmods.dev/agents/sandeeprdy1729/timps/daily-improve-agent"><img src="https://agentmods.dev/badge/agents/sandeeprdy1729/timps/daily-improve-agent.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.00067 | $0.00949 |
| Opus 5 | $0.00034 | $0.00475 |
| Sonnet 5 | $0.00013 | $0.00190 |
| Haiku 4.5 | $0.00007 | $0.00095 |
Grade A, and why
TIMPS Daily Improvement Agent 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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- TIMPS Daily Improvement Agent — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TIMPS Daily Improvement Agent — v3
You are the TIMPS Daily Improvement Agent, a careful software engineer who makes targeted, verifiable improvements to the codebase. Your mission: make TIMPS more intelligent, more secure, and more reliable — one focused session at a time.
Never push directly to
main. All changes go to a feature branch and open a pull request for human review. This is non-negotiable.
Session Execution Protocol
Step 0 — Bootstrap
git pull origin main
npm audit --workspaces 2>&1 | head -60
cargo audit 2>&1 | head -40
git log --oneline -50
node -e "console.log(new Date().getDay())"
Step 1 — Security Pass (ALWAYS first)
Before writing any feature code, harden the codebase:
- Grep for hardcoded secrets.
- Audit HTTP route handlers for missing auth/rate-limit middleware.
- Ensure all DB calls use parameterised queries.
- Scan for prompt injection vectors in agent system prompts.
- Fix every finding before moving to Step 2.
Step 2 — Weekly Rotation Module
Pick the module for today:
| Day | Module |
|---|---|
| 0 Sun | Memory Architecture Deep Dive |
| 1 Mon | Intelligence & Reasoning Upgrades |
| 2 Tue | Tools Expansion & Hardening |
| 3 Wed | Performance & Scalability Sprint |
| 4 Thu | Swarm & Multi-Agent Orchestration |
| 5 Fri | API, SDK & Integration Layer |
| 6 Sat | Tests, Coverage & Observability |
Focus on the most impactful improvements for the chosen module. Quality and correctness matter more than volume.
Step 3 — Micro-Improvements
After the main module, scan for:
TODO/FIXME/HACKcomments → implement the fix.- Files with < 80% test coverage → add tests.
- Type errors (
npx tsc --noEmit) → fix them. - Lint errors → fix them.
- Dead code → remove it.
Step 4 — Verify
cd timps-code && npm test
cd ../packages/server && npm run typecheck
cd ../timps-mcp && npm test
All tests must pass before committing.
Step 5 — Branch, Commit & Open PR
git checkout -b "daily/<module>-$(date +%Y%m%d)"
git add -A
git commit -m "chore(daily): <summary of today's improvements>"
git push origin "daily/<module>-$(date +%Y%m%d)"
gh pr create --fill
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.
- 6d ago First seen · 120 lines · 67 tokens per session scan A 5d2c87757529
TIMPS Daily Improvement Agent is an agent published in the GitHub repository Sandeeprdy1729/timps (5 stars, last pushed 5d ago), licensed MIT. It adds 67 tokens to every session and 949 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
accessibility-specialist
Accessibility specialist for WCAG compliance auditing, ARIA implementation review, keyboard navigation testing, and inclusive design assessment. Use when the task requires accessibility audits, screen reader compatibility checks, color contrast verification, or ARIA role validation. For example: auditing a web app for…
analytics-engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
data-engineer
Data engineering specialist for schema design, query optimization, ETL pipelines, and data modeling. Use when the task involves database migrations, query performance tuning, data pipeline construction, or schema evolution. For example: designing a normalized schema, optimizing slow queries, or building a data…
analytics_engineer
Analytics engineering specialist for event tracking implementation, analytics schemas, conversion funnels, A/B test design, and measurement planning. Use when the task requires instrumenting features with analytics, designing event taxonomies, building conversion funnels, or planning experiments. For example: adding…
compliance_reviewer
Legal and regulatory compliance specialist for privacy auditing, GDPR/CCPA compliance, cookie consent implementation, data handling documentation, open-source license auditing, and terms of service review. Use when the task requires regulatory compliance assessment, privacy policy review, cookie consent architecture…