Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/jody09-dotcom/constructionx-skills/ghl-stage-update)<a href="https://agentmods.dev/skills/jody09-dotcom/constructionx-skills/ghl-stage-update"><img src="https://agentmods.dev/badge/skills/jody09-dotcom/constructionx-skills/ghl-stage-update/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/skills/jody09-dotcom/constructionx-skills/ghl-stage-update"><img src="https://agentmods.dev/badge/skills/jody09-dotcom/constructionx-skills/ghl-stage-update.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.00111 | $0.01301 |
| Opus 5 | $0.00056 | $0.00651 |
| Sonnet 5 | $0.00022 | $0.00260 |
| Haiku 4.5 | $0.00011 | $0.00130 |
Grade A, and why
ghl-stage-update 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 10d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GHL Stage Update
Move a contact through GoHighLevel pipeline stages with a single command. Replaces the click-through flow in the GHL UI (search contact, click opportunity, change stage, add note, set follow-up) with one structured input.
The skill reads from your GoHighLevel sub-account using a Private Integration token. It does not store data anywhere except GHL itself. Every action is logged to GHL's audit trail under the API user.
When to Use
- After a sales call where a contact moves stage (e.g. "Replied" -> "Interested" -> "Booked Call")
- After sending a follow-up where you want to log the touch and reset the next-follow-up date
- When clearing a backlog of stale GHL stage updates that piled up while you focused on conversations
- When you want a one-line audit trail of pipeline movement without opening the GHL UI
Do NOT use this skill to:
- Create new contacts (use GHL UI, contact form, or a different tool)
- Change pipeline structure (stages, pipelines themselves)
- Send messages or trigger workflows
Prerequisites
Set these environment variables before running:
GHL_API_KEY=pk_your_private_integration_token
GHL_LOCATION_ID=your_sub_account_location_id
You can put them in a .env file in your project root if you use a dotenv loader, or export them in your shell. The skill itself does not load .env.
To find the values:
- API key: GHL UI -> Settings -> Private Integrations -> Create new token. Required scopes:
contacts.readonly,contacts.write,opportunities.readonly,opportunities.write. Store the token securely; it cannot be retrieved after creation. - Location ID: GHL UI -> Settings -> Business Profile -> Location ID. Or call
GET /locationsif you have agency access.
Workflow
Phase 1, gather inputs.
Ask the user for the following. If anything is missing, ask one short follow-up question, do not guess.
- Contact (required): Name or email. Name is fuzzy-matched; email is exact-matched. If multiple contacts share the same name and have no distinguishing email, the script returns the candidate list with IDs and you re-run with
--contact-id <id>instead of--contact. - Target stage (required): The destination stage name. Fuzzy-matched against pipeline stages.
- Pipeline (optional): Pipeline name. If omitted, the skill checks all pipelines and flags ambiguity if the contact has opportunities in more than one.
- Note (optional): Free-text note appended to the contact's notes log with a timestamp.
- Next follow-up (optional): ISO date
YYYY-MM-DDor natural-language ("next Tuesday", "in 7 days"). If natural-language, resolve to ISO before passing to the script.
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.
- 10d ago First seen · 120 lines · 111 tokens per session scan A 60e6d17ad49b
ghl-stage-update is a skill published in the GitHub repository Jody09-dotcom/constructionx-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 111 tokens to every session and 1,301 once invoked, about $0.0006 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 skills, from other repositories
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
Statutory Interpretation
Use when applying a disciplined analytical method to parse and interpret a statutory, regulatory, or contractual provision — mapping structure, defined terms, and competing readings — to produce a structured interpretation worksheet for attorney review.
hardening
A set of Linux instructions for hardening systems, meaning reducing unsafe settings and limiting unnecessary access.
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
google-ads-audit
Google Ads account audit and business context setup. Use for account-health audits and business-context setup. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should I fix in my ads", or when the user is new to NotFair and hasn't run…
data-charts-tako
Search and visualize the world's data - get charts, insights, and embeddable knowledge cards for finance, economics, demographics, sports, and more.