claude-code-best-practice is a repository of agents, commands, skills, hooks, plugins, and configuration guidance for Claude Code. It helps developers organize repeatable workflows and apply agentic engineering practices, including in monorepos. The catalogue entries are its reusable Claude Code workflow components.
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/shanraisshan/claude-code-best-practice/time-agentgit clone --depth 1 https://github.com/shanraisshan/claude-code-best-practiceWrote 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/shanraisshan/claude-code-best-practice/time-agent)<a href="https://agentmods.dev/agents/shanraisshan/claude-code-best-practice/time-agent"><img src="https://agentmods.dev/badge/agents/shanraisshan/claude-code-best-practice/time-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 | $0.00037 | $0.00279 |
| Opus 5 | $0.00018 | $0.00139 |
| Sonnet 5 | $0.00007 | $0.00056 |
| Haiku 4.5 | $0.00004 | $0.00028 |
Grade A, and why
time-agent-pkt 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- time-agent-pkt — 100% identical, 0 lines differ
What it actually says
Time Agent
You are a specialized agent that displays the current time in Pakistan Standard Time (PKT).
Your Task
Display the current date and time in Pakistan Standard Time (UTC+5).
Instructions
-
Run the following bash command:
TZ='Asia/Karachi' date '+%Y-%m-%d %H:%M:%S %Z' -
Return the result in this format:
Current Time in Pakistan (PKT): YYYY-MM-DD HH:MM:SS PKT
Requirements
- Always use the
Asia/Karachitimezone (UTC+5) - Use 24-hour format
- Include the date alongside the time
- Keep the output concise
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 · 46 lines · 37 tokens per session scan A 2403e94c7b94
time-agent-pkt is an agent published in the GitHub repository shanraisshan/claude-code-best-practice (65,596 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 279 once invoked, about $0.0002 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-30.
Other agents, from other repositories
security-reviewer
Use proactively when attacker-controlled input, trust boundaries, authorization decisions, sensitive sinks, secrets, or security-impacting changes require exploitability analysis. Do not use for generic correctness review without a meaningful security boundary.
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
migration-upgrade-prompt
Use this when: planning or executing a framework, runtime, database, or major-dependency migration, or a toolchain swap, without downtime. Skip to: Protocol · Phase 1: MAP · Codemods first · Phase 4: RISK-ASSESS · Remember.
architect
System architect responsible for component boundaries, integration points, data flow, ADRs, technology selection, and API contracts. Invoke for architecture decisions, dependency strategy, performance planning, and interface design. Read-only — produces decisions and documentation.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.