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.
git clone --depth 1 https://github.com/o2alexanderfedin/strategic-research-automation-templateWrote 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/commands/o2alexanderfedin/strategic-research-automation-template/update-context)<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/update-context"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/update-context/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/o2alexanderfedin/strategic-research-automation-template/update-context"><img src="https://agentmods.dev/badge/commands/o2alexanderfedin/strategic-research-automation-template/update-context.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00323 |
| Opus 5 | $0.00000 | $0.00161 |
| Sonnet 5 | $0.00000 | $0.00065 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
update-context 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 12d 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
Update Context Files
Objective
Update project context files based on new information or changing requirements.
Usage
/update-context
Context Files to Review
1. Company Profile (context/company-profile.md)
Review and update:
- Company capabilities and core competencies
- Strategic goals and priorities
- Constraints and limitations
- Available resources (team, budget, infrastructure)
- Recent developments or changes
2. Client Information (context/client-info.md)
Review and update:
- Client background and industry position
- Client goals and success criteria
- Client constraints (budget, timeline, regulatory)
- Stakeholder preferences
- Communication preferences
3. Industry Background (context/industry-background.md)
Review and update:
- Industry trends and dynamics
- Regulatory landscape changes
- Competitive environment shifts
- Technology advancements
- Market conditions
Update Process
1. Review Existing Context
- Read current context files
- Identify outdated information
- Note gaps in coverage
2. Gather New Information
- Research recent developments
- Interview stakeholders (if applicable)
- Review internal documents
- Monitor industry news
3. Update Files
- Revise outdated sections
- Add new relevant information
- Remove obsolete content
- Maintain consistent format
4. Validate Impact
- Identify active sprints that may be affected
- Consider re-running analysis if context changes significantly
- Document rationale for major changes
Output
- Updated context files
- Change log documenting updates
- Impact assessment on active/completed sprints
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.
- 12d ago First seen · 65 lines · 0 tokens per session scan A 571c73f5fef6
update-context is a command published in the GitHub repository o2alexanderfedin/strategic-research-automation-template (19 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 323 tokens. 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 commands, from other repositories
sessions
Manage Claude Code session history, aliases, and session metadata.
save-session
Save current session state to a dated file in /.claude/session-data/ so work can be resumed in a future session with full context.
resume-session
Load the most recent session file from /.claude/session-data/ and resume work with full context from where the last session ended.
learn-eval
Extract reusable patterns from the session, self-evaluate quality before saving, and determine the right save location (Global vs Project).
instinct-import
Import instincts from file or URL into project/global scope.
instinct-export
Export instincts from project/global scope to a file.