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-log-callWrote 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-log-call)<a href="https://agentmods.dev/skills/dorianschlede/nexus-template/hubspot-log-call"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/hubspot-log-call/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-log-call"><img src="https://agentmods.dev/badge/skills/dorianschlede/nexus-template/hubspot-log-call.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.00042 | $0.00657 |
| Opus 5 | $0.00021 | $0.00329 |
| Sonnet 5 | $0.00008 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
hubspot-log-call 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 11d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Log HubSpot Call
Specialized skill for logging call engagements 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
--title- Call title (required)
Optional Parameters
--body- Call notes/summary--duration- Duration in minutes (default: 0)--direction- OUTBOUND or INBOUND (default: OUTBOUND)--status- COMPLETED, BUSY, NO_ANSWER, etc. (default: COMPLETED)
Examples
Log completed call:
uv run python 00-system/skills/hubspot/hubspot-master/scripts/log_call.py \
--title "Discovery Call with Acme" \
--body "Discussed requirements, timeline, and budget. Next step: send proposal." \
--duration 30 \
--json
Log missed call:
uv run python 00-system/skills/hubspot/hubspot-master/scripts/log_call.py \
--title "Follow-up attempt" \
--status "NO_ANSWER" \
--direction "OUTBOUND" \
--json
Call Status Values
| Status | Meaning |
|---|---|
| COMPLETED | Call connected |
| BUSY | Line busy |
| NO_ANSWER | No answer |
| FAILED | Call failed |
| CANCELED | Call canceled |
Output Format
{
"id": "14772074448",
"properties": {
"hs_call_title": "Discovery Call with Acme",
"hs_call_body": "Discussed requirements...",
"hs_call_direction": "OUTBOUND",
"hs_call_duration": "1800000",
"hs_call_status": "COMPLETED",
"hs_timestamp": "2025-12-13T10:00:00Z"
}
}
Display Format
[OK] Call logged!
ID: 14772074448
Title: Discovery Call with Acme
Direction: Outbound
Duration: 30 minutes
Status: Completed
Notes: Discussed requirements, timeline...
Error Handling
| Error | Solution |
|---|---|
| 401 | Invalid token - re-run setup |
| 403 | Missing crm.objects.calls.write scope |
| 429 | Rate limited - wait and retry |
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.
- 11d ago First seen · 112 lines · 42 tokens per session scan A 08d4791979bd
hubspot-log-call is a skill published in the GitHub repository DorianSchlede/nexus-template (8 stars, last pushed 7mo ago), licensed MIT. It adds 42 tokens to every session and 657 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.