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.
git clone --depth 1 https://github.com/DorianSchlede/nexus-templatenpx agentmods add skills/dorianschlede/nexus-template/hubspot-update-dealWrote 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/dorianschlede/nexus-template/hubspot-update-deal)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/hubspot-update-deal"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/hubspot-update-deal/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/dorianschlede/nexus-template/hubspot-update-deal"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/hubspot-update-deal.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.00044 | $0.00766 |
| Opus 5 | $0.00022 | $0.00383 |
| Sonnet 5 | $0.00009 | $0.00153 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
hubspot-update-deal 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update HubSpot Deal
Specialized skill for updating deals in HubSpot CRM.
Pre-Flight Check
Before running, execute config check:
uv run python 00-system/skills/hubspot/hubspot-master/scripts/check_hubspot_config.py --json
If ai_action is not proceed_with_operation, follow hubspot-connect setup guide.
Usage
Required Parameters
--id- Deal ID (required)
Optional Parameters (at least one required)
--name- New deal name--amount- New deal value--stage- New deal stage--closedate- New close date (YYYY-MM-DD)
Examples
Update stage (move deal):
uv run python 00-system/skills/hubspot/hubspot-master/scripts/update_deal.py \
--id 5840795376 \
--stage "closedwon" \
--json
Update amount:
uv run python 00-system/skills/hubspot/hubspot-master/scripts/update_deal.py \
--id 5840795376 \
--amount 75000 \
--json
Close deal as won:
uv run python 00-system/skills/hubspot/hubspot-master/scripts/update_deal.py \
--id 5840795376 \
--stage "closedwon" \
--closedate "2025-12-13" \
--json
Common Deal Stages
| Stage ID | Name |
|---|---|
| appointmentscheduled | Appointment Scheduled |
| qualifiedtobuy | Qualified to Buy |
| presentationscheduled | Presentation Scheduled |
| decisionmakerboughtin | Decision Maker Bought In |
| contractsent | Contract Sent |
| closedwon | Closed Won |
| closedlost | Closed Lost |
Finding Deal ID
If user says "close the Acme deal", first search:
uv run python 00-system/skills/hubspot/hubspot-master/scripts/search_deals.py --name "Acme" --json
Then use the returned ID for the update.
Output Format
{
"id": "5840795376",
"properties": {
"dealname": "Acme Corp - Enterprise",
"amount": "75000",
"dealstage": "closedwon",
"hs_lastmodifieddate": "2025-12-13T10:30:00Z"
}
}
Display Format
[OK] Deal updated!
ID: 5840795376
Name: Acme Corp - Enterprise
Updated fields:
- stage: Closed Won
- amount: $75,000
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 · 132 lines · 44 tokens per session scan A 39f16a43b591
hubspot-update-deal is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 44 tokens to every session and 766 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-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.