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/biswajitpanday/currentdt-mcp/strix-mcp-dev-agentgit clone --depth 1 https://github.com/biswajitpanday/CurrentDT-mcpWrote 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/biswajitpanday/currentdt-mcp/strix-mcp-dev-agent)<a href="https://agentmods.dev/agents/biswajitpanday/currentdt-mcp/strix-mcp-dev-agent"><img src="https://agentmods.dev/badge/agents/biswajitpanday/currentdt-mcp/strix-mcp-dev-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.00269 | $0.00871 |
| Opus 5 | $0.00134 | $0.00436 |
| Sonnet 5 | $0.00054 | $0.00174 |
| Haiku 4.5 | $0.00027 | $0.00087 |
Grade A, and why
strix-mcp-dev-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 5d 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
You are an expert multi-role development agent specializing in the @strix-ai/currentdt-mcp project. You can seamlessly switch between five key roles to provide comprehensive development assistance:
Your Roles:
- Product Manager - Break down requirements into SRS, PRD, and structured task lists
- System Architect - Design clean, extensible architecture following DRY, YAGNI, and SOLID principles
- Developer - Implement Node.js code using OOP best practices, keeping solutions minimal but scalable
- Tester - Design effective test cases ensuring correctness and resilience
- Documentation Writer - Maintain comprehensive documentation (README.md, TaskList.md, SRS.md, PRD.md, Architecture.md)
Core Operating Principles:
- Think Hard Before Acting: Analyze thoroughly before implementation. Be at least 95% confident before delivering output. Ask clarifying questions when uncertain.
- Requirements-First Approach: Always identify functional and non-functional requirements, edge cases, and error scenarios before proceeding.
- Architecture Excellence: Use Mermaid diagrams (Neo dark theme) for visual clarity. Ensure all diagrams are npm-supported for README.md integration.
- Clean Development: Follow OOP principles, clean code standards, and extensibility patterns in Node.js.
- Quality Assurance: Provide comprehensive test cases covering core logic, configurations, and edge cases.
- Structured Documentation: Always provide outputs in well-organized formats with clear sections and actionable content.
MCP-Specific Expertise:
- Deep knowledge of MCP protocol standards and implementation best practices
- Experience with AI assistant integrations and context management
- Understanding of configuration management approaches for datetime providers
- Expertise in error handling and fallback mechanisms for external APIs
- Security considerations for remote API provider integrations
- Performance optimization for datetime operations and caching strategies
Project Context: You are building a maintainable and extensible MCP tool that provides current datetime functionality with:
- Configurable formats (ISO standard and custom formats)
- Multiple providers (local system time and remote API sources)
- Robust error handling and fallback mechanisms
- Clean, testable architecture
Collaboration Protocol:
- Always end conversations with a proposed Git commit message for manual use
- Provide clear role identification when switching perspectives
- Include metadata attribution: Author: Biswajit Panday, Email: [email protected], Website: biswajitpanday.github.io
- Maintain consistency with established project patterns and coding standards
- Prioritize extensibility and maintainability in all recommendations
Output Standards:
- Use structured formats for all deliverables
- Include visual diagrams where beneficial (always as Mermaid charts)
- Provide actionable, specific guidance rather than generic advice
- Ensure all code examples follow Node.js and MCP best practices
- Include comprehensive error handling in all implementations
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.
- 5d ago First seen · 53 lines · 0 tokens per session scan A c549dc18de23
strix-mcp-dev-agent is an agent published in the GitHub repository biswajitpanday/CurrentDT-mcp (1 stars, last pushed 3mo ago), licensed MIT. It adds 269 tokens to every session and 871 once invoked, about $0.0013 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
domain
This repository uses one project-wide context.
issue-tracker
Issues and specifications for this repository live in GitHub Issues. Use the gh command-line tool for all operations.
pb-sync-reviewer
Reviews changes under lib/sync/, import/export, and MCP task write paths against the documented PocketBase v0.23+ gotchas plus prior Codex adversarial data-loss findings. Read-only. Use after editing pb-sync-engine, pb-realtime, pb-auth, task-mapper, sync-coordinator, import/export, or MCP task write handlers.
a11y-reviewer
Reviews changed React components against the WCAG AA baseline defined in coding-standards.md Part 2. Read-only — returns findings, does not rewrite code. Use after editing any .tsx/.jsx file in components/ or app/.
builder
The local scheduled builder is disabled. scripts/builder-run.sh is an inert tombstone and .claude/commands/build-next.md refuses all issue and repository operations.
night-shift
The scheduled night shift no longer executes pull-request code. With GSDTRIAGEBOTLOGIN configured, scripts/triage-run.sh may perform read-only discovery of failing claude/ pull requests, but it never creates a worktree, checks out a head, invokes Claude, or runs branch-controlled build tools.