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 skills/grcengineering/companion/profile-refreshernpx skills add grcengineering/companion --skill profile-refreshergit clone --depth 1 https://github.com/grcengineering/companionWrote 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/skills/grcengineering/companion/profile-refresher)<a href="https://agentmods.dev/skills/grcengineering/companion/profile-refresher"><img src="https://agentmods.dev/badge/skills/grcengineering/companion/profile-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 | $0.00055 | $0.00471 |
| Opus 5 | $0.00028 | $0.00235 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
profile-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 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.
What it actually says
profile-refresher
What
Refresh learner-owned profile context after meaningful learning or role changes. In static/local-first mode this is learner-initiated; future signed-in mode may schedule it.
When
- The learner's goals may have changed.
- The learner has several session notes.
- The Companion's profile feels stale.
- A path or lab is miscalibrated because context changed.
Not For
- First profile creation. Use
profile-wizard. - Tracking concept status. Use
progress-tracker. - Updating the Companion brain.
Inputs
- Current learner profile.
- Recent session notes or learner-provided summary.
profile/learner-profile.schema.json.
Steps
Ask three prompts:
- What has changed in your role, environment, or goals since we last calibrated?
- What concepts now feel clearer than before?
- What still feels confusing, avoided, or too hard?
Then propose a profile diff. Do not silently apply it.
Validation
- The update is expressed as a visible diff.
- The learner can accept, edit, or discard it.
- Changed fields still match the schema and contain no sensitive identifiers.
Gotchas
- If the learner has no existing profile, route to
profile-wizard. - Do not infer sensitive behavioural analytics such as time-of-day patterns without explicit opt-in.
- If only progress changed, update progress state rather than profile identity.
Failure Modes
- Silent profile mutation: always show the diff.
- Overfitting from one session: mark uncertain updates as tentative.
- Brain drift: never update files under
brain/.
Examples
- Learner says their goals changed from audit to GRC engineering -> Ask the three refresh prompts and propose a goal diff.
- Learner says the Companion keeps over-explaining basics -> Update current level and known concepts, pending approval.
- Learner says "I learned vendor review this week" -> Route concept status to
progress-tracker, not profile identity.
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.
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 · 64 lines · 55 tokens per session scan A 8831580d77af
profile-refresher is a skill published in the GitHub repository grcengineering/companion (32 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 471 once invoked, about $0.0003 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 skills, from other repositories
control-mapping
Maps NIST controls to FedRAMP requirements and documents. Use when helping with control implementation, compliance mapping, security baseline alignment, or understanding control requirements.
frmr-analysis
Analyzes FedRAMP FRMR documents to extract control mappings, KSI entries, and version changes. Use when the user asks about FedRAMP requirements, control mappings, compliance data, or needs to understand FRMR document content.
GRC & Compliance
Governance, risk, and compliance — risk assessment and scoring, control mapping across NIST CSF 2.0 / ISO 27001:2022 / SOC 2 / CIS Controls v8, gap analysis, audit evidence preparation, and security policy generation.
performing-soc2-type2-audit-preparation
Automates SOC 2 Type II audit preparation including gap assessment against AICPA Trust Services Criteria (CC1-CC9), evidence collection from cloud providers and identity systems, control testing validation, remediation tracking, and continuous compliance monitoring. Covers all five TSC categories (Security…
mapping-builder
Build a reviewed crosswalk (RequirementMappingSet YAML library + review xlsx/csv) between two CISO Assistant framework YAML files using Claude itself as the reasoning engine. Zero infrastructure — stdlib + pyyaml only, no embedders, no LM Studio, no Qdrant. Use when the user asks to map / crosswalk / generate a…
reference-controls-enricher
Enrich a CISO Assistant framework YAML by linking each assessable requirement to reference control URNs from the central doc-pol library (CISO Assistant Key Reference Controls). Produces a reviewable xlsx and patches the framework YAML in place. Use when the user asks to "add reference controls to framework X", "link…