「credential」の検索結果

Android APK decompiler that converts DEX bytecode to readable Java source code. Use when you need to decompile APK files, analyze app logic, search for vulnerabilities, find hardcoded credentials, or understand app behavior through readable source code.

日本語の概要は準備中です。原文の説明を表示しています。

Use telnet to interact with IoT device shells for pentesting operations including device enumeration, vulnerability discovery, credential testing, and post-exploitation. Use when the user needs to interact with network-accessible shells, IoT devices, or telnet services.

日本語の概要は準備中です。原文の説明を表示しています。

Best-practices reference for preparing and instrumenting applications on Temps. Covers the app runtime contract (`.temps.yaml` health, HOST/PORT, readiness, SIGTERM, replicas, migrations) and production observability (errors, traces, metrics, logs, analytics, privacy, sampling, cardinality, credential boundaries). Use whenever building or reviewing an app for Temps, configuring health checks, adding telemetry, diagnosing missing/noisy signals, or checking OTLP/Sentry/analytics ingestion. Triggers include "temps best practices", "prepare this app for Temps", ".temps.yaml health", "temps health check", "ignore health checks in otel", "temps observability", "wire up telemetry", and "instrument this app for temps". Prefer focused setup skills for a single SDK. Use temps-cli for executing deploy and resource-management commands.

日本語の概要は準備中です。原文の説明を表示しています。

Provision, verify, and connect a self-hosted Temps platform instance on an explicitly authorized machine. Use when the user wants an agent to install Temps with the official deploy script, configure a local CLI context, start browser device authorization, present the approval URL, wait for approval, or perform initial platform, DNS, TLS, user, and service setup without exposing credentials.

日本語の概要は準備中です。原文の説明を表示しています。

Detect exposed secrets, API keys, credentials, and tokens in code. Use before commits, on file saves, or when security is mentioned. Prevents accidental secret exposure. Triggers on file changes, git commits, security checks, .env file modifications.

日本語の概要は準備中です。原文の説明を表示しています。

Configure or change the approved worker models for codex-on-crack, inspect available models and compatibility, preview role files, or undo a setup. The user selects the lead in Codex. Setup preserves root settings, credentials, unrelated agents, and config.toml.

日本語の概要は準備中です。原文の説明を表示しています。

Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials.

日本語の概要は準備中です。原文の説明を表示しています。

Escalate blocked runs to a human via configured channel or fallback to BLOCKED.md and exit the loop. Use when the loop hits an ambiguous spec, a missing credential, a destructive action needing approval, or 3+ consecutive verify failures on the same task.

日本語の概要は準備中です。原文の説明を表示しています。

Use the official Sentry CLI to investigate issues, events, traces, and logs for Vibe Remote without committing Sentry credentials into the repository.

日本語の概要は準備中です。原文の説明を表示しています。

Use Avibe Vault for API keys, tokens, passwords, protected credentials, authenticated HTTP requests, or digest signing without exposing secret values to the agent.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, light browser lane. The one routine in this kit with an outward surface. Takes the slots that are due today, whose drafts were written yesterday and passed the copy check, whose hold box is not ticked, and whose destination the member wrote into the publish allow list themselves, and hands each one to the channel the member configured. It records a receipt the instant each slot lands. It never drives a browser control to publish, never replies, sends only where you released the channel a message, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly, on a Friday, read only everywhere. Scores the week from the kit's own ledgers with a source path beside every number, cuts it by platform, framework, pillar, slot time, and post length, rewrites the drafting standards from that evidence and from nothing else, replays the browser flows the other routines depend on, and files exactly one thing to stop and one to do more of. It publishes only where you released the channel, never replies, spends only where you released it, never touches a credential, and never writes a number it did not measure.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, heavy browser lane. Captures the dated raw material tomorrow's drafts are built from, out of the member's own shipped work, their own site and changelog, their own signed in saved searches, and the places their audience already is. Every line carries a source URL read this run, a date, a verbatim quote, and an expiry. It invents nothing, it is read only everywhere and totally read only on LinkedIn, and it sends only where you released the channel, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, file work only, no browser at all. Reads every ledger and run record since its cursor, resolves which drafted changes actually merged by reading the commit graph rather than a dashboard, closes and reopens incidents on that evidence, folds the card inbox, re-renders the review board, and writes the short morning brief the member opens first. It never merges, never deploys, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Runs once by hand on the first day and once a month after that, on the first weekday, light browser lane. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the pipeline, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed to the files it owns, and carries every member written setting across verbatim. It holds every outbound action unless you released the channel, and it never enters a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, browser only when a source refuses to be fetched. Works the single card the standup marked next: reads the shared publishing standard and the card's specification, pulls the live result set for the primary keyword, reads the pages currently ranking, writes the body, the metadata, the internal links and the outbound authority links, generates and compresses a hero, and leaves a complete draft folder with one ready line. It never opens a publishing surface, never touches a live property, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, heavy browser lane. Reads the member's own saved searches and the named sources for one buyer segment, captures candidate accounts together with the contactable people attached to them, scores every row against the named tests in the qualification file, and writes each one with the evidence that qualified it. Read only on every people surface, LinkedIn included. It holds every outbound action unless you released the channel, and it never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Monthly, browser conditional. On its first run it discovers the member's properties from the sites they name, writes the three strategy files, creates every ledger and folder the kit reads, files the opening cards, and registers the eight scheduled jobs. Every month after that it re-reads the evidence rather than its own previous conclusions, rebuilds the topic map and the internal link map, corrects any property fact it can prove wrong, and records every change with the path of the evidence that forced it. It holds publishing and spending unless you released the channel, and it never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly, on a Friday, read only everywhere. Scores the week from the ledgers with a source path beside every number, replays the browser flows the other routines depend on, names one thing to kill and one thing to scale, and files both as cards. It sends only where you released the channel, spends only where you released it, never touches a credential, and never writes a number it did not count out of a named file this run.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, heavy browser lane, two halves in one run. First it reads the member's own mailbox for replies on the threads the ledger says were sent and records them. Only then does it work out who is due a follow up, write each one into a dated queue file, and compose it into the mailbox as an unsent draft. It holds every outbound action unless you released the channel, and it never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, browser only when the card needs one. Takes the next ready cards off the launch board and does the work each one names: stages copy into the dashboard, fills a directory or press form and leaves it open in its tab, verifies a setup, packages a handoff, or researches its own next targets. It ticks its own card the moment it has verified the file that closes it. It submits only where you released the channel, sends only where you released the channel, spends only where you released it, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, heavy browser lane. Selects the qualified people who have never been written to, drafts each one a first touch into a dated queue file the member reads, and composes each passing draft into the member's own mailbox as an unsent draft. It verifies by the Drafts count and never by a toast. It holds every outbound action unless you released the channel, and it never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekly, file work only, no browser at all. Reads everything the week produced, picks exactly three moves, and argues both sides of each one before the member reads a word of it, with every clause carrying a number or an observation from a file it names. It argues against its own top recommendation last, records a predicted effect and the metric that would show it so the monthly review can score it, and files each move onto the register. It sends only where you released the channel, spends only where you released it, never deploys, and never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。

Weekdays, file work only, no browser at all. Reads every ledger, queue file, and run record written since its own cursors, turns the member's ticks into sent rows and closed cards, folds the card inbox, re-renders the pipeline board, and writes the short morning brief the member opens first. It names the veto window every day. It holds every outbound action unless you released the channel, and it never touches a credential.

日本語の概要は準備中です。原文の説明を表示しています。