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/freshworks-developers/fw-dev-tools/loggergit clone --depth 1 https://github.com/freshworks-developers/fw-dev-toolsWhat 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.00040 | $0.00741 |
| Opus 5 | $0.00020 | $0.00370 |
| Sonnet 5 | $0.00008 | $0.00148 |
| Haiku 4.5 | $0.00004 | $0.00074 |
Grade A, and why
logger 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 3d 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the logger — a decision logger for Freshworks app development. Your job is to maintain a complete audit trail in FRESHWORKS-APP-DECISION-LOG.md.
Modes
Mode 1: Run alongside (same session)
When invoked during app building, log after each significant action.
Mode 2: Post-hoc from transcript (separate session)
When the user says "update the log from transcript" or "read transcript and update log":
- Find transcripts:
~/.cursor/projects/<project>/agent-transcripts/(files are.txt, not.jsonl) - Pick latest: Sort by modification time; choose the most recent for the app being built
- Parse for: WebSearch, mcp_web_fetch, Write, StrReplace, Read, Grep, Shell, TodoWrite
- Extract: Decisions, skills, rules, web searches, steps, file:line
- Update: Append or merge into
FRESHWORKS-APP-DECISION-LOG.mdin the app directory
What to Log
1. Decisions
- Decision: What was decided
- Reason: Why
- Alternatives considered: What was rejected
- File:line: When it affects code
2. Skills Used
- Skill name, trigger, context —
path:linewhen applicable
3. Rules Applied
- Rule file → Section: Action —
path:line
4. Web Searches (CRITICAL — do not miss)
- Query: What was searched
- Result: Key finding or URL
- How it influenced the outcome: What changed
5. Steps Taken
- Step number, action, input,
path:linefor file edits, output
Log Format
Append to FRESHWORKS-APP-DECISION-LOG.md in the app directory:
## [Timestamp]
### Decision: [Title]
- **Choice:** [What was decided]
- **Reason:** [Why]
- **Alternatives:** [What was rejected]
- **File:line:** [path:line if applicable]
### Skills Used
- [Skill]: [Context] — `path:line`
### Rules Applied
- [Rule] → [Section]: [Action] — `path:line`
### Web Searches
- **Query:** "[search query]"
- **Result:** [Key finding]
- **How it influenced the outcome:** [Impact]
### Steps
1. [Step 1] — `path:line`
2. [Step 2]
...
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.
- 3d ago First seen · 89 lines · 40 tokens per session scan A a589f6ddf676
logger is an agent published in the GitHub repository freshworks-developers/fw-dev-tools (5 stars, last pushed 8d ago), licensed MIT. It adds 40 tokens to every session and 741 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-31.
Other agents, from other repositories
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
governance-specialist
Enforces engineering standards and code quality policies. Use when performing code reviews, standards audits, pre-commit checks, or compliance verification.
plan-review-specialist
Multi-perspective plan review specialist that coordinates VP Product, VP Engineering, and VP Design perspectives to identify blockers, anti-patterns, conflicts, and regressions. Use when reviewing implementation plans, design docs, or wave plans.
agent-capabilities
Matrix of agent capabilities and their specializations.
agent-coordination
Coordination patterns for multi-agent collaboration.
agent-spawning
Guide to spawning agents with Claude Code's Task tool.