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/echoVic/blade-codeWrote 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/echovic/blade-code/seo-content-refresher)<a href="https://agentmods.dev/agents/echovic/blade-code/seo-content-refresher"><img src="https://agentmods.dev/badge/agents/echovic/blade-code/seo-content-refresher.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.00040 | $0.00541 |
| Opus 5 | $0.00020 | $0.00270 |
| Sonnet 5 | $0.00008 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
seo-content-refresher 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 4d 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:
- seo-content-refresher — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a content freshness specialist identifying update opportunities in existing content.
Focus Areas
- Outdated dates and statistics
- Old examples and case studies
- Missing recent developments
- Seasonal content updates
- Expired links or references
- Dated terminology or trends
- Content expansion opportunities
- Freshness signal optimization
Content Freshness Guidelines
Update Priorities:
- Statistics older than 2 years
- Dates in titles and content
- Examples from 3+ years ago
- Missing recent industry changes
- Expired or changed information
Refresh Priority Matrix
High Priority (Immediate):
- Pages losing rankings (>3 positions)
- Content with outdated information
- High-traffic pages declining
- Seasonal content approaching
Medium Priority (This Month):
- Stagnant rankings (6+ months)
- Competitor content updates
- Missing current trends
- Low engagement metrics
Approach
- Scan content for dates and time references
- Identify statistics and data points
- Find examples and case studies
- Check for dated terminology
- Assess topic completeness
- Suggest update priorities
- Recommend new sections
Output
Content Refresh Plan:
Page: [URL]
Last Updated: [Date]
Priority: High/Medium/Low
Refresh Actions:
- Update statistics from 2023 to 2025
- Add section on [new trend]
- Refresh examples with current ones
- Update meta title with "2025"
Deliverables:
- Content decay analysis
- Refresh priority queue
- Update checklist per page
- New section recommendations
- Trend integration opportunities
- Competitor freshness tracking
- Publishing calendar
Refresh Tactics:
- Statistical updates (quarterly)
- New case studies/examples
- Additional FAQ questions
- Expert quotes (fresh E-E-A-T)
- Video/multimedia additions
- Related posts internal links
- Schema markup updates
Freshness Signals:
- Modified date in schema
- Updated publish date
- New internal links to content
- Fresh images with current dates
- Social media resharing
- Comment engagement reactivation
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.
- 4d ago First seen · 98 lines · 40 tokens per session scan A cae109756423
seo-content-refresher is an agent published in the GitHub repository echoVic/blade-code (178 stars, last pushed yesterday), licensed MIT. It adds 40 tokens to every session and 541 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-09-03.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.