[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M758YTFF1KDCNNAD94TER1BP":3,"skill-same:01M758YTFF1KDCNNAD94TER1BP":50},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M758YTFF1KDCNNAD94TER1BP","secure-credential-handling",null,"Handle passwords, API keys, tokens, and secrets securely when using terminal\u002Fread_file\u002Fexecute_code tools — avoid exposing sensitive values in tool call parameters or chat output.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity\u002Fsecure-credential-handling\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: secure-credential-handling\ndescription: Handle passwords, API keys, tokens, and secrets securely when using terminal\u002Fread_file\u002Fexecute_code tools — avoid exposing sensitive values in tool call parameters or chat output.\nversion: 1.0.0\nauthor: Steadfaste Fleet\ntrigger: before reading or passing any credential file, password, API token, or secret\n---\n\n# Secure Credential Handling\n\n**Core principle:** tool call parameters (especially `terminal` commands and `read_file` paths) are VISIBLE in full in the chat. Every session sees every command string. Treat terminal command strings as a public log.\n\n## Hard Rules\n\n### 1. Never write the secret value into a command string\n\n```bash\n# ❌ WRONG — password appears as literal text in the tool call\nprintf 's3cur3-p@ss' > \u002Ftmp\u002Fpasswd_clean.txt\ncurl -u \"admin:s3cur3-p@ss\" https:\u002F\u002F...\n\necho 'ghp_xxxxxxxxxxxx' | gh auth login --with-token\n\n# ✅ RIGHT — password never appears in tool call text\n# Use cat from file in $() — expands AFTER tool call is sent\ncurl -sk --basic -u \"root:$(cat ~\u002F.asus)\" https:\u002F\u002F...\n\n# Read tokens from file via stdin redirect\ngh auth login --with-token \u003C ~\u002F.github_token_path\n```\n\n### 2. Never use read_file on credential files\n\n```bash\n# ❌ WRONG — read_file displays the file contents in chat output\nread_file(path=\"~\u002F.asus\")\n\n# ✅ RIGHT — check file with safe alternatives\nwc -l ~\u002F.asus              # just count lines\nstat ~\u002F.asus                # file metadata only\necho \"password saved\"       # you know it exists, no need to display\n```\n\n### 3. For repeated use, stage to a temp file silently\n\n```python\n# Copy credential to temp file ONCE (terminal shows cp command, not content)\nterminal(\"cp ~\u002F.asus \u002Ftmp\u002Fpasswd_clean.txt\")\n\n# Then reference via $() subshell on every subsequent command\nterminal(\"curl -sk -u \\\"root:$(cat \u002Ftmp\u002Fpasswd_clean.txt)\\\" https:\u002F\u002F...\")\n```\n\n**Why this works:** `$(cat \u002Ftmp\u002Fpasswd_clean.txt)` in a terminal tool call shows the file path but NOT the file content. The shell expands it after the command is displayed.\n\n## Defense Layers\n\nThree layers protect against credential leaks in `terminal()` commands:\n\n1. **Behavioral** — this skill + SOUL.md principle on every agent\n2. **Pre-commit scan** — `secret-leak-detector.sh` runs in `pre-commit-score` hook, scans staged files for printf\u002Fecho + credential patterns\n3. **Runtime watchdog** — `secret-leak-watchdog` (no_agent cron, every 4h) scans cron outputs and session files for leaked patterns, alerts via inbox\n\nSet `SKIP_SECRET_SCAN=1` to bypass the pre-commit detector (emergencies only).\n\n## Pitfalls\n\n### printf with literal secret\n```bash\n# EXPOSES the password — printf shows the value in the command string\nprintf 'myP@ssw0rd!' > \u002Ftmp\u002Fpass.txt\n```\n**Fix:** `cp ~\u002Fsecret_file \u002Ftmp\u002Fpass.txt` — no content leakage.\n\n### Shell `&` in password causes silent truncation\nIf the password contains `&` and you use inline `$(cat ~\u002Ffile)`, the shell expansion is fine within `$()`. But if you accidentally paste the password directly into the command, the `&` background-processes the rest. Always use a file reference, never inline.\n\n### Context-echoing edit tools leak secrets from SURROUNDING lines\nA `patch`\u002Ffind-and-replace tool returns a **diff with context lines**. Editing a\ncomment in a secret-bearing file (`.env`, `auth.json`, an env file) prints the\nneighbouring `KEY=value` lines into the chat, even though the edit itself was\ntrivial. On 2026-10-02 a live provider key reached the session transcript this way,\nvia a one-word comment rename in `.env`.\n- **Never** use a context-echoing edit tool on a file that holds secrets, however\n  small the edit. A cosmetic change never justifies touching such a file.\n- If such a file genuinely must change, edit without echoing: `sed -i` from the\n  shell shows only the command string, not the affected lines.\n- Reading the value for a scan: `V=$(sed -n 's\u002F^NAME=\u002F\u002Fp' file)` in a subshell and\n  print **counts** — never the value.\n\n### Terminal output vs command display\nThe `terminal` tool shows the `command` parameter in full. Even though this is tool metadata (not standard output), it IS visible to the user and recorded in the session log. Treat it as a broadcast channel.\n\n### Base64 encoding for Basic Auth\nWhen you need HTTP Basic Auth: let curl handle it with `-u \"user:$(cat \u002Ftmp\u002Fpass)\"`. The base64 encoding happens on the server side of curl, never in your visible command string.\n","# Secure Credential Handling\n\n**Core principle:** tool call parameters (especially `terminal` commands and `read_file` paths) are VISIBLE in full in the chat. Every session sees every command string. Treat terminal command strings as a public log.\n\n## Hard Rules\n\n### 1. Never write the secret value into a command string\n\n```bash\n# ❌ WRONG — password appears as literal text in the tool call\nprintf 's3cur3-p@ss' > \u002Ftmp\u002Fpasswd_clean.txt\ncurl -u \"admin:s3cur3-p@ss\" https:\u002F\u002F...\n\necho 'ghp_xxxxxxxxxxxx' | gh auth login --with-token\n\n# ✅ RIGHT — password never appears in tool call text\n# Use cat from file in $() — expands AFTER tool call is sent\ncurl -sk --basic -u \"root:$(cat ~\u002F.asus)\" https:\u002F\u002F...\n\n# Read tokens from file via stdin redirect\ngh auth login --with-token \u003C ~\u002F.github_token_path\n```\n\n### 2. Never use read_file on credential files\n\n```bash\n# ❌ WRONG — read_file displays the file contents in chat output\nread_file(path=\"~\u002F.asus\")\n\n# ✅ RIGHT — check file with safe alternatives\nwc -l ~\u002F.asus              # just count lines\nstat ~\u002F.asus                # file metadata only\necho \"password saved\"       # you know it exists, no need to display\n```\n\n### 3. For repeated use, stage to a temp file silently\n\n```python\n# Copy credential to temp file ONCE (terminal shows cp command, not content)\nterminal(\"cp ~\u002F.asus \u002Ftmp\u002Fpasswd_clean.txt\")\n\n# Then reference via $() subshell on every subsequent command\nterminal(\"curl -sk -u \\\"root:$(cat \u002Ftmp\u002Fpasswd_clean.txt)\\\" https:\u002F\u002F...\")\n```\n\n**Why this works:** `$(cat \u002Ftmp\u002Fpasswd_clean.txt)` in a terminal tool call shows the file path but NOT the file content. The shell expands it after the command is displayed.\n\n## Defense Layers\n\nThree layers protect against credential leaks in `terminal()` commands:\n\n1. **Behavioral** — this skill + SOUL.md principle on every agent\n2. **Pre-commit scan** — `secret-leak-detector.sh` runs in `pre-commit-score` hook, scans staged files for printf\u002Fecho + credential patterns\n3. **Runtime watchdog** — `secret-leak-watchdog` (no_agent cron, every 4h) scans cron outputs and session files for leaked patterns, alerts via inbox\n\nSet `SKIP_SECRET_SCAN=1` to bypass the pre-commit detector (emergencies only).\n\n## Pitfalls\n\n### printf with literal secret\n```bash\n# EXPOSES the password — printf shows the value in the command string\nprintf 'myP@ssw0rd!' > \u002Ftmp\u002Fpass.txt\n```\n**Fix:** `cp ~\u002Fsecret_file \u002Ftmp\u002Fpass.txt` — no content leakage.\n\n### Shell `&` in password causes silent truncation\nIf the password contains `&` and you use inline `$(cat ~\u002Ffile)`, the shell expansion is fine within `$()`. But if you accidentally paste the password directly into the command, the `&` background-processes the rest. Always use a file reference, never inline.\n\n### Context-echoing edit tools leak secrets from SURROUNDING lines\nA `patch`\u002Ffind-and-replace tool returns a **diff with context lines**. Editing a\ncomment in a secret-bearing file (`.env`, `auth.json`, an env file) prints the\nneighbouring `KEY=value` lines into the chat, even though the edit itself was\ntrivial. On 2026-10-02 a live provider key reached the session transcript this way,\nvia a one-word comment rename in `.env`.\n- **Never** use a context-echoing edit tool on a file that holds secrets, however\n  small the edit. A cosmetic change never justifies touching such a file.\n- If such a file genuinely must change, edit without echoing: `sed -i` from the\n  shell shows only the command string, not the affected lines.\n- Reading the value for a scan: `V=$(sed -n 's\u002F^NAME=\u002F\u002Fp' file)` in a subshell and\n  print **counts** — never the value.\n\n### Terminal output vs command display\nThe `terminal` tool shows the `command` parameter in full. Even though this is tool metadata (not standard output), it IS visible to the user and recorded in the session log. Treat it as a broadcast channel.\n\n### Base64 encoding for Basic Auth\nWhen you need HTTP Basic Auth: let curl handle it with `-u \"user:$(cat \u002Ftmp\u002Fpass)\"`. The base64 encoding happens on the server side of curl, never in your visible command string.\n",{"name":5,"author":24,"trigger":25,"version":26,"description":7},"Steadfaste Fleet","before reading or passing any credential file, password, API token, or secret","1.0.0","main","2e6aa8d15ab0a366c90be54f61bf9c6e97015e83","skills\u002Fsecurity\u002Fsecure-credential-handling",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill secure-credential-handling",{"tool":42,"command":43},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill secure-credential-handling",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill secure-credential-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fsecurity\u002Fsecure-credential-handling\u002FSKILL.md",true,[],[51,59,66,73,80,87],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":58},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":58},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":58},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":58},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":58},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":58},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]