review-rep-call-trends

review-rep-call-trends is a skill for Codex from evoelsewhere/evoflux. It costs 55 tokens per session (2,270 once invoked), scanned A, a copy of review-rep-call-trends, Apache-2.0.

A sales-call analysis workflow that compares a representative's older and newer calls. It identifies changes in behaviour over time and supports evidence-based coaching.

In plain words
What is it for?
Use it to review call trends, identify coaching actions, and select calls worth listening to again. It does not create trackers, send feedback, or save other work products.
Why use it?
It turns scattered call examples into a clear view of improvement, decline, and stable habits instead of relying on memory or impressions.

Skill for Codex

Written for Codex: agents/openai.yaml present.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is {Follow the instructions and output format/conditions in [Limitations and Improvements](../index/SKILL.md#limitations-and-improvements)}.

Good fit Use it to review call trends, identify coaching actions, and select calls worth listening to again. It does not create trackers, send feedback, or save other work products.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/evoelsewhere/evoflux
agentmods
npx agentmods add skills/evoelsewhere/evoflux/review-rep-call-trends

Made for: Codex.

Wrote 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.

agentmods badge for review-rep-call-trends

README.md
[![agentmods](https://agentmods.dev/badge/skills/evoelsewhere/evoflux/review-rep-call-trends/github.svg)](https://agentmods.dev/skills/evoelsewhere/evoflux/review-rep-call-trends)
Your own site
<a href="https://agentmods.dev/skills/evoelsewhere/evoflux/review-rep-call-trends"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/review-rep-call-trends/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.

agentmods 80×15 button for review-rep-call-trends

Your own site · 80×15
<a href="https://agentmods.dev/skills/evoelsewhere/evoflux/review-rep-call-trends"><img src="https://agentmods.dev/badge/skills/evoelsewhere/evoflux/review-rep-call-trends.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,270 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00055 $0.02270
Opus 5 $0.00028 $0.01135
Sonnet 5 $0.00011 $0.00454
Haiku 4.5 $0.00006 $0.00227

Measured 2d ago against content hash 93dbaf5c3f21, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

review-rep-call-trends 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 2d 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.

Origin

This is a copy

100% identical to review-rep-call-trends — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

app/agent/builtin_skills/sales/references/workflows/review-rep-call-trends/SKILL.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Context-Gathering Intake

Whenever this skill asks for context, strongly prefer using the answers-ask-user-input skill and the ask_user_input tool over other tools such as request_user_input; otherwise ask directly in the conversation.

Turn a representative time-based call sample into objective coaching guidance. This skill compares older and newer call evidence to identify genuine improvement, regression, and stable patterns. It owns the readout only; it does not create trackers, send feedback, post messages, or save artifacts.

Common Skill Instructions

MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.

Key Dependency Categories

These categories are particularly important for this workflow; use other sources only when they materially improve sampling or interpretation.

  • [Blocking] ~~Meeting Transcripts for time-sliced call search, summaries, transcript moments, speaker context, dates, companies, and clickable call links. It blocks the default live-source trend path; explicit older/newer call evidence already in context satisfies the need.
  • ~~Knowledge & Files for user-provided or exported transcripts, call summaries, manager-provided call sets, and prior coaching context

Call summaries or transcripts are required for trend claims. Manager notes, CRM outcomes, and generic impressions may provide context, but cannot substitute for older-versus-newer call evidence. If the sample is small or skewed, return a limited trend readout rather than overgeneralizing.

Reference Loading

SKILL.md owns the normal time-sliced trend workflow and output format. Load references only when their extra detail matters:

Read the full file on GitHub · 161 lines

Files

What ships with it

3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

  1. 2d ago First seen · 161 lines · 55 tokens per session scan A 93dbaf5c3f21

Subscribe to this mod's changes

review-rep-call-trends is a skill published in the GitHub repository evoelsewhere/evoflux (7 stars, last pushed 2d ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,270 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-rep-call-trends, differing in 0 lines, and is treated as a copy.