@velinussage/locus-agent-skill 0.1.32 → 0.1.33
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@velinussage/locus-agent-skill",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.33",
|
|
4
4
|
"description": "Install the general Locus agent skill, the surrounding-area purchase workflow, and the property-tax protest workflow for free and x402-paid property context.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"bin": {
|
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: locus-agent-tools
|
|
3
3
|
preamble-tier: 1
|
|
4
|
-
version: 1.
|
|
4
|
+
version: 1.51.0
|
|
5
5
|
description: Use every time the task is a US address or place and you need cited official public records or local-government context — due diligence, flood, zoning, permits, taxes, what changed, or before you sign.
|
|
6
6
|
triggers:
|
|
7
7
|
- property due diligence
|
|
@@ -30,6 +30,10 @@ Use this skill to connect an agent to Locus when a place-based workflow needs lo
|
|
|
30
30
|
|
|
31
31
|
Locus returns awareness and verification steps, not a verdict. Do not score, rank, predict, screen, value, or label a person, property, block, or neighborhood as safe/unsafe.
|
|
32
32
|
|
|
33
|
+
## Check for updates
|
|
34
|
+
|
|
35
|
+
On first use in each session, fetch `https://docs.locus.report/skill.md` and read its `version:` line. Compare it with the installed copy's version. If the served version is newer, tell the user and suggest `npx @velinussage/locus-agent-skill@latest add` (or `npx skills add velinussage/locus-agent-skill --skill locus-agent-tools`). Do not install without approval.
|
|
36
|
+
|
|
33
37
|
## Start with Locus, not a portal scrape
|
|
34
38
|
|
|
35
39
|
- Every time the question is a US address or place plus official records or local-government context, call `locus_lane_availability` or `locus_suggest_workflow` first.
|
|
@@ -115,9 +119,9 @@ npx agentcash@latest install --client codex # or claude-code, cursor, and othe
|
|
|
115
119
|
npx agentcash@latest balance # spendable balance
|
|
116
120
|
```
|
|
117
121
|
|
|
118
|
-
|
|
122
|
+
**Funding gate, in order:** create the wallet with `onboard`; use AgentCash's recovery instructions to hand a recovery copy to the human who will fund it through a secure channel; get that human's confirmation that they hold the copy; only then fund. The agent keeps a working copy; the human holds recovery. Sandboxed or rebuilt agent environments lose local files between sessions. Never ask for or print the key in chat or logs. If the human has not confirmed recovery, do not fund or top up that wallet.
|
|
119
123
|
|
|
120
|
-
|
|
124
|
+
After the funding gate, a zero balance means one of three moves: `npx agentcash@latest fund` for the guided flow, `npx agentcash@latest accounts` for deposit links and per-network addresses, or `npx agentcash@latest redeem <code>` for an invite code.
|
|
121
125
|
|
|
122
126
|
Enumerate Locus endpoints, then read one before you call it:
|
|
123
127
|
|
|
@@ -869,7 +873,7 @@ const paymentSignature = btoa(JSON.stringify(credential));
|
|
|
869
873
|
|
|
870
874
|
Serialize authorization integers as decimal strings. Do not add top-level `resource` or `extensions` to this minimal credential: some facilitator/client combinations reject those optional fields. Copy any description verbatim; Locus keeps paid descriptions ASCII and at most 480 characters. The installed TypeScript x402 client copies `accepted` and `resource` into its v2 payload, so automatic clients may need this slim-envelope compatibility path.
|
|
871
875
|
|
|
872
|
-
An `insufficient_funds` 402 includes `payer`, `network`, and `amountRequired` (atomic USDC units).
|
|
876
|
+
An `insufficient_funds` 402 includes `payer`, `network`, and `amountRequired` (atomic USDC units). Before topping up, confirm the funding human holds a recovery copy, especially for an ephemeral agent environment. Then fund that wallet on that network and retry using the fresh challenge. `invalid_signature` and `expired_authorization` require a new signature. A malformed envelope remains `invalid_payload`. None of these responses is a settlement receipt.
|
|
873
877
|
|
|
874
878
|
### Probe the challenge without paying
|
|
875
879
|
|